engine
wolfssl
| engine | wolfssl | |
|---|---|---|
| 1 | 12 | |
| 351 | 2,179 | |
| 1.7% | 1.2% | |
| 4.4 | 9.9 | |
| about 1 month ago | 7 days ago | |
| C | 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.
engine
-
CryptoLyzer: A comprehensive cryptographic settings analyzer
It is not just a theory. A special fork of OpenSSL, maintained by Pluralsight author Peter Mosmans, aims to have as many ciphers as possible. This fork is used and recommended by Mozilla Cipherscan, however, it can offer less than two hundred cipher suites, but there are more than three hundred in the different RFCs according to Cipher Suite Info. The majority of them are weak or insecure, which makes it particularly important to be part of the analysis. In addition, it is also true that there are cipher suites that are not on the Cipher Suite Info list, for instance, Russian standard (GOST) cipher suites. These are rarely used cipher suites, but there is an OpenSSL engine that implements them, so they should be checked.
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?
tls-scan - An Internet scale, blazing fast SSL/TLS scanner ( non-blocking, event-driven )
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.
sslyze - Fast and powerful SSL/TLS scanning library.
esp-idf - Espressif IoT Development Framework. Official development framework for Espressif SoCs.
OpenSSL - TLS/SSL and crypto library
GmSSL - 支持国密SM2/SM3/SM4/SM9/SSL的密码工具箱
openssl - 'Extra featured' OpenSSL with ChaCha20 and Poly1305 support
openssl - Provides SSL, TLS and general purpose cryptography.
testssl.sh - Testing TLS/SSL encryption anywhere on any port
Crypto++ - free C++ class library of cryptographic schemes
cipherscan - A very simple way to find out which SSL ciphersuites are supported by a target.
pyOpenSSL -- A Python wrapper around the OpenSSL library - A Python wrapper around the OpenSSL library