search

eduardsui / tlse

Single C file TLS 1.2/1.3 implementation, using tomcrypt as crypto library
Other
540 stars 89 forks source link

Merge into tomcrypt #70

Closed stokito closed 2 years ago

stokito commented 2 years ago

Hi, just found your project and maybe you can answer my questions. Firts of all: did you tried to merge your TLS implementation into the libtomcrypt? Or it should be as a separate project.

The libtomcrypt is used by droobear and as far I understood that's the main usage of the lib and almost nobody else doesn use it. Is it right?

The OpenWrt uses dropbear but the libtomcrypt is staticly compiled into DB so nobody else can't use it. Recently OpenWrt added HTTPS support out of the box but they devided to use WolfSSL. So now any OpenWrt device has two crypto libraries: tomcrypt and wolfssl. Many other packages like emailrelay are still depends on OpenSSL so now I have three libs on my router :) The WolfSSL also have their ssh implementation which potentially can replace the Dropbear. Is it possible somehow to solve the mess? Or each library has it's own fetures and all software can't reuse the same.

Sorry for asking you, hope you know better. Thank you

eduardsui commented 2 years ago

Hello! I think is better to keep the two libraries separated. TLSe uses only a small subset of all the tomcrypt features. Also, I know that there are forks using NaCl or other cryptolibraries. Cryptographic libraries and network protocol libraries require different skillsets. But, tlse being a single-c-file library, integrating into tomcrypt is plug and play.

stokito commented 2 years ago

Thank you for the quick response.