Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MTPROTO Support #1

Closed
chaoticryptidz opened this issue Jan 9, 2019 · 4 comments
Closed

MTPROTO Support #1

chaoticryptidz opened this issue Jan 9, 2019 · 4 comments
Assignees
@SapphicCode
Labels
enhancement New feature or request protocol-request Protocol implementation request

Comments

@chaoticryptidz
Copy link
Contributor

It would be quite nice if you added support for these protocols.
MTPROTO Docs: https://core.telegram.org/mtproto
@SapphicCode SapphicCode self-assigned this Jan 10, 2019
@SapphicCode
Copy link
Owner

I'll look into it.

@SapphicCode SapphicCode added the enhancement New feature or request label Jan 10, 2019
@chaoticryptidz
Copy link
Contributor Author

See #2

@SapphicCode
Copy link
Owner

As for MTProto support, I'll still need to look into the handshake for it. Likely just going to use Wireshark when I find the time.

@SapphicCode SapphicCode changed the title SOCKS4/5 Support and MTPROTO Support MTPROTO Support Jan 31, 2019
@SapphicCode SapphicCode added the protocol-request Protocol implementation request label Jan 31, 2019
@SapphicCode
Copy link
Owner

Okay, so, having looked at the TCP transport dumps I can infer that they're just an encrypted blob, which can't really be matched against, so I'm merging this issue with #4. Either use the fallback once implemented, or use a reverse proxy in combination with the HTTP transport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SapphicCode SapphicCode

Labels
enhancement New feature or request protocol-request Protocol implementation request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SapphicCode @chaoticryptidz