tlspuffin
wolfssl
Our great sponsors
| tlspuffin | wolfssl | |
|---|---|---|
| 2 | 12 | |
| 123 | 2,173 | |
| 3.3% | 2.1% | |
| 7.0 | 9.9 | |
| 6 days ago | 5 days ago | |
| Rust | C | |
| Apache License 2.0 | GNU General Public License v3.0 only |
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.
tlspuffin
-
Keeping the Wolves Out of WolfSSL
LibAFL served as a basis for this project.
Fuzzer source: https://github.com/tlspuffin/tlspuffin
- tlspuffin: A symbolic-model-guided fuzzer for TLS
wolfssl
-
“Purchasing an arm”
Or something a bit more lightweight - https://github.com/wolfSSL/wolfssl
- WolfSSL
- Security Advisory 2022-10-04-1 - wolfSSL buffer overflow during a TLS 1.3 handshake (CVE-2022-39173)
- Getting started with wolfssl
-
Ask HN: Can a TCP connection be MitM attacked if already established?
> 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/
- 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
- WolfSSL Release 5.0.0
What are some alternatives?
AFLplusplus - The fuzzer afl++ is afl with community patches, qemu 5.1 upgrade, collision-free coverage, enhanced laf-intel & redqueen, AFLfast++ power schedules, MOpt mutators, unicorn_mode, and a lot more!
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.
ssldump - ssldump - (de-facto repository gathering patches around the cyberspace)
esp-idf - Espressif IoT Development Framework. Official development framework for Espressif SoCs.
VulnTLS - Collection of TLS vulnerabilities ready to be exploited.
GmSSL - 支持国密SM2/SM3/SM4/SM9/SSL的密码工具箱
bananafzz - Banana Fuzzer ~ modulable, loop based, poc gen, code cov, platform agnostic, race oriented
openssl - Provides SSL, TLS and general purpose cryptography.
Crypto++ - free C++ class library of cryptographic schemes
pyOpenSSL -- A Python wrapper around the OpenSSL library - A Python wrapper around the OpenSSL library
e2guardian - E2guardian is a web content filter that can work in proxy, transparent or icap server modes
OpenSSL - TLS/SSL and crypto library