[Feature Request] Do any plan to realize trojan using libev, just like shadowsocks-libev for low-power consumption router device

[0neday]

• I certify that I have read the contributing guidelines and I acknowledge if I don't follow the format below or I don't check this box, my issue will be closed immediately without any notice.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I find trojan binary have 2M bytes, and using more memory than ss-redir and ss-tunnel, so is it possible, that realize it using libev or pure c language, thx.

Is this problem relevant to what trojan should care about?
Trojan is a protocol implementation, not a full-fledged proxy client. Features such as custom routing will not be accepted.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[0neday]

and trojan depend on boost library and openssl tls1.3, that is difficult to compile it on old low-power consumption router device using openwrt 17.0-18.0

[0neday]

and trojan depend on boost library and openssl tls1.3, that is difficult to compile it on old low-power consumption router device using openwrt 17.0-18.0

just for test

[Chigusa0w0]

It is unwise and error-prone to implement TLS by ourselves. As trojan current supports only OpenSSL, even with libev you still need to compile OpenSSL. Which renders the porting pointless.
Enough lessons tell us that any attempt to create a cryptographic secure communication protocol from sketch by amateurs is potentially unsecure and exploitable. Trojan is created to fix the mistake, not to repeat it.

[0neday]

It is unwise and error-prone to implement TLS by ourselves. As trojan current supports only OpenSSL, even with libev you still need to compile OpenSSL. Which renders the porting pointless.

Enough lessons tell us that any attempt to create a cryptographic secure communication protocol from sketch by amateurs is potentially unsecure and exploitable. Trojan is created to fix the mistake, not to repeat it.

Thx for reply in detail, I have found a compromise method for fixing it.

[0neday]

have compiled static trojan armv7 binary, 0neday/Exploit-HS8545M-ONT@8a1592e

[GreaterFire]

@0neday nope