e2guardian VS wolfssl

Try e2guardian.

e2Guardian (Filtering & block ads at URL level for privacy) https://github.com/e2guardian/e2guardian

Looks like Squid has limited ability to filter by key words. However there used to be a software called dansguardian (looks like it was bought out). There is now a fork called e2guardian https://github.com/e2guardian/e2guardian/wiki

This could be done using something like E2guardian (a fork / successor to DansGuardian). It can be configured to block:

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