snif VS wolfssl

The VESmail account manager guides though the setup process and provides the settings for your email client app to connect to the local VESmail app. For the convenience of the setup, the account manager suggests to use a trusted TLS connection via an end-to-end SNIF relay (https://snif.host), although a direct non-TLS connection to localhost (IMAP 7143, SMTP 7125) can be used instead.

That link (https://github.com/vesvault/snif/graphs/traffic) redirects to github.com because that is probably restricted to repository owners only. Try making the link https://github.com/vesvault/snif/

https://snif.host https://github.com/vesvault/snif

Or something a bit more lightweight - https://github.com/wolfSSL/wolfssl

> I have no room for TLS on micro computer

How micro is your micro? There are embedded TLS stacks such as wolfSSL[1]. If you carefully select the cipher suite and certificate requirements, and perhaps limit TLS payload sizes, you may be able to fit on a lot more systems than you initially suspect. x.509 is expensive in code space though, if that's the constraint, you may do better with an application specific certificate replacement of some sort.

[1] https://www.wolfssl.com/

There are many notable open-source projects (SSLyze, CipherScan, testssl.sh, tls-scan, …) and several SaaS solutions (CryptCheck, CypherCraft, Hardenize, ImmuniWeb, Mozilla Observatory, SSL Labs, …) to do a security setting analysis, especially when we are talking about TLS, which is the most common and popular cryptographic protocol. However, most of these tools heavily depend on one or more versions of one or more cryptographic protocol libraries, like GnuTLS, OpenSSL, or wolfSSL. But why is this such a problem?

wolfSSL 5.0.0