wolfSSL has removed CheckOcspResponderChain(), a non-compliant chain walk that authorized any OCSP responder certificate issued by any ancestor of the target certificate’s issuer as of version 5.9.2. RFC 6960 §4.2.2.2 requires that an OCSP response be signed directly by the CA that issued the certificate in question or a delegated responder appointed by that exact […]
Read MoreMore TagCategory: wolfSSL/ wolfCrypt
wolfSSL Improves TLS 1.3 Alert Compliance for Missing SNI
wolfSSL now sends the correct alert when a TLS 1.3 server requires the Server Name Indication (SNI) extension and the client fails to include it. Previously, the server sent a generic handshake_failure alert; it now sends the missing_extension alert defined by RFC 8446 for exactly this case. TLS 1.2 and earlier keep the existing handshake_failure […]
Read MoreMore TagwolfSSL Relaxes Serial Number Validation for Root CA Certificates
wolfSSL has refined its X.509 serial number validation to better handle real-world trust stores. Previously, wolfSSL rejected any certificate with a serial number of 0. While RFC 5280 requires CAs to issue certificates with positive serial numbers, some long-standing self-signed root CA certificates in circulation were created with serial 0, and rejecting them caused otherwise […]
Read MoreMore TagwolfSSL Now Available for Zephyr’s Secure Sockets Layer
We’re pleased to announce that wolfSSL can now be integrated directly into the secure sockets layer of the Zephyr RTOS. The required patches are available now in our Open Source Project (OSP) repository. What This Means These patches let you swap out mbedTLS and use wolfSSL as the TLS provider behind Zephyr’s native socket API. […]
Read MoreMore TagA Quantum Safety Net for TLS 1.3: Mandatory PSKs with Certificate Authentication
TLS 1.3 normally forces a choice: authenticate with certificates or with a pre-shared key, but not both in the same handshake. Combining them gives you a second, independent root of trust that survives even if the first one falls — and wolfSSL now supports both doing this and requiring it. The foundation is RFC 8773, […]
Read MoreMore TagStateful Hash-Based Signatures (LMS and XMSS) in X.509 Certificates
wolfSSL now supports the stateful hash-based signature schemes LMS/HSS and XMSS/XMSS^MT in X.509 certificates, following RFC 9802. What’s New Both sides of the certificate lifecycle are covered: Generation – Sign certificates and CSRs with an LMS/HSS or XMSS/XMSS^MT key, encoded exactly as RFC 9802 specifies. Verification – Parse and verify certificate chains that use these […]
Read MoreMore TagwolfCrypt on the TI C2000 C28x: PQC ML-DSA/ML-KEM on a 16-bit-byte DSP
We’re excited to share that wolfCrypt now runs a full modern crypto suite on Texas Instruments’ C2000 C28x – the NIST post-quantum schemes ML-DSA (FIPS 204) and ML-KEM (FIPS 203), plus RSA, Diffie-Hellman, AES, ChaCha20-Poly1305, HMAC/HKDF, the Curve25519/Ed25519, Curve448/Ed448, and NIST P-256 elliptic-curve schemes, and the SHA-1/2/3 and SHAKE hash families – all validated on […]
Read MoreMore TagwolfSSL adds LMS and XMSS to wolfHSM
LMS and XMSS are stateful hash-based signature schemes (NIST SP 800-208) suited to long-lived firmware and code signing. wolfSSL has added support for both post-quantum cryptographic (PQC) algorithms to wolfHSM. This feature leverages the hardware security module (HSM) to securely and persistently store the “stateful” key and counter for both algorithms, as well as perform […]
Read MoreMore TagMbedOS End of Life; but wolfSSL on MbedOS lives on
MbedOS goes into End-of-Life in July this year, but as we are committed to our customers and their security, we will still support wolfSSL product on MbedOS going forward. If you’re in a pinch with CRA or other security requirements, feel free to contact us at facts@wolfssl.com, and we’ll work out a plan with you […]
Read MoreMore TagIntroducing tinytls13: A minimal TLS 1.3 build profile that fits a complete client in about 30 KB of flash.
In brief. tinytls13 is a new wolfSSL build profile for deeply constrained devices. It compiles a complete, working TLS 1.3 client in about 30.8 KB of flash on an ARM Cortex-M33, with no X.509 and no extras you did not ask for. Why we built it Secure boot, attestation, and IoT connectivity increasingly need TLS […]
Read MoreMore Tag