wolfssl
sslyze
Our great sponsors
wolfssl | sslyze | |
---|---|---|
12 | 10 | |
2,147 | 3,109 | |
1.9% | - | |
9.9 | 6.5 | |
6 days ago | 9 days ago | |
C | Python | |
GNU General Public License v3.0 only | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wolfssl
-
“Purchasing an arm”
Or something a bit more lightweight - https://github.com/wolfSSL/wolfssl
- Security Advisory 2022-10-04-1 - wolfSSL buffer overflow during a TLS 1.3 handshake (CVE-2022-39173)
- The project with a single 11,000-line code file
- Information and learning resources for cryptography newcomers
-
CryptoLyzer: A comprehensive cryptographic settings analyzer
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?
-
FOSS News International #2: November 8-145, 2021
wolfSSL 5.0.0
-
Max HTTPS throughput on ESP32?
You mention mbedtls, but for an example I was able to find that wolfssl lists some benchmarks and notice that under hardware acceleration, AES CBC gives OK performance while AES GCM looks pretty bad.
sslyze
- SSL Diag Tool
- SSL / TLS scanning utility (internal) ?
-
sslyze VS cryptolyzer - a user suggested alternative
2 projects | 24 Jan 2022
-
CryptoLyzer: A comprehensive cryptographic settings analyzer
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?
- Create a tool to capture the TLS handshake and cipher suite being used
-
Awesome Penetration Testing
SSLyze - Fast and comprehensive TLS/SSL configuration analyzer to help identify security mis-configurations.
What are some alternatives?
mbedTLS - An open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API. Releases are on a varying cadence, typically around 3 - 6 months between releases.
sslscan - sslscan tests SSL/TLS enabled services to discover supported cipher suites
esp-idf - Espressif IoT Development Framework. Official development framework for Espressif SoCs.
GmSSL - 支持国密SM2/SM3/SM4/SM9/SSL的密码工具箱
openssl - Provides SSL, TLS and general purpose cryptography.
pyOpenSSL -- A Python wrapper around the OpenSSL library - A Python wrapper around the OpenSSL library
Crypto++ - free C++ class library of cryptographic schemes
e2guardian - E2guardian is a web content filter that can work in proxy, transparent or icap server modes
OpenSSL - TLS/SSL and crypto library
snif - SNIF ~ e2e TLS trust for IoT
RustScan - 🤖 The Modern Port Scanner 🤖
merecat - Small and made-easy HTTP/HTTPS server based on Jef Poskanzer's thttpd