Missing instruction about settting up for "EE" (faketls+padding) mode

[msva]

Hi there!
It seems there is no instruction about how to settt up this proxy to (properly) work in "EE" mode (fake-tls + padding (as in "DD" mode)).

tdlib (and so is Telegram X), and official desktop telegram client (tdesktop) have a checks, that for EE mode key should have a length of 20 or more bytes (excluding EE prefix, or >=21 including it).

And MTProxy forces to set a key (for -S) of 32 digits (16 bytes), which is only acceptable for "DD" prefix.

But, on the other hand, code looks like it do support "EE" mode 🤷‍♂️

So, it is hard to understand, how to set this up to work with FakeTLS+padding ("EE") mode...

// by the way, official Android client kinda "works" with changing DD to EE in the secret, but I had a discussion with @john-preston (author of Telegram Desktop), and he investigated this a bit, and he found that it (android client) just disables even padding (nott even enables faketls) in that case (EE + short 16 bit key).
Same for iOS client and Telegram For Mac.
And Telegram X (semi-official android client based on tdlib) doesn't support "ee" with short keys either (as tdesktop).

[preston]

FYI you have the wrong "Preston" :)

[msva]

FYI you have the wrong "Preston" :)

Yeah, thanks, fixed (he is @preston on tg, and here he is @john-preston) 😁