Hello
I’ve been experimenting a bit with Telegram’s MTProto and RPC. I think that in a modern implementation, we could completely do away with OpenSSL. It’s an overly heavy dependency that causes a lot of complications - not just during the build process.
In my solution, I implemented the Crypton module for this purpose. I added the implementation of all the necessary algorithms to it, and the solution became simpler.
https://github.com/isopen/ton-ai-core/tree/master/packages/core/src/crypton
Next, Crypton makes use of MTProto, the TL language, and transport layers in the other modules as needed. As a result, my telegram-agent successfully connects to Telegram servers and completes authorization.
https://github.com/isopen/ton-ai-core/tree/master/agents/telegram-agent
Why don't you want to support your crypto layer?
Hello
I’ve been experimenting a bit with Telegram’s MTProto and RPC. I think that in a modern implementation, we could completely do away with OpenSSL. It’s an overly heavy dependency that causes a lot of complications - not just during the build process.
In my solution, I implemented the Crypton module for this purpose. I added the implementation of all the necessary algorithms to it, and the solution became simpler.
https://github.com/isopen/ton-ai-core/tree/master/packages/core/src/crypton
Next, Crypton makes use of MTProto, the TL language, and transport layers in the other modules as needed. As a result, my
telegram-agentsuccessfully connects to Telegram servers and completes authorization.https://github.com/isopen/ton-ai-core/tree/master/agents/telegram-agent
Why don't you want to support your crypto layer?