wolfSSL Embedded SSL/TLS; FIPS 140-3

wolfSSL Embedded SSL/TLS; FIPS 140-3

@wolfssl.com

The most popular open source, embedded TLS. Active in #IoTSecurity, #Avionics, #Automotive & more. Over 5B connections secured! #TLS13 #SecureYourConnectivity

131 followers17 following1.2K posts

From QMA architecture to validation: see how wolfCrypt and wolfTPM support EigenQ’s post-quantum integration path. Join wolfSSL and EigenQ for a technical walkthrough covering ML-DSA, ML-KEM, and TPM 2.0 v1.85 post-quantum algorithm support. 🗓️ Oct 28 | 9 AM PT

🔐 Moving OpenSSL cryptography to wolfSSL? Choose the integration that fits your version. wolfEngine supports OpenSSL 1.x. wolfProvider supports OpenSSL 3.x/4.x and enables post-quantum algorithms like ML-KEM and ML-DSA. Learn more: www.wolfssl.com/wolf... #OpenSSL #PQC #FIPS #MLKEM #MLDSA

wolfssl.comwolfEngine vs wolfProvider - wolfSSLAt wolfSSL we provide two main services to help with the transition away from OpenSSL crypto operations, wolfEngine and wolfProvider. These both provide a

Building a FIPS 140-3 architecture on Yocto Linux takes more than integration. You also need to generate the required configuration, run module self-tests, and verify cryptographic operations. Join our webinar to get the practical details! Save the date: Oct 27 at 9 AM PT.

Want wolfCrypt powering crypto across your Zephyr applications? 🔐 wolfPSA brings Zephyr support for the PSA Crypto API, with FIPS 140-3 options, post-quantum algorithms, and hardware acceleration—all without linking mbedTLS code. Learn more:

wolfssl.comwolfPSA: Replacing Zephyr's Mbed TLS PSA Crypto Provider - wolfSSLLast month we announced wolfSSL as a TLS provider for Zephyr's secure sockets layer. That work covered the networking side of the stack. Today we are

Keep private keys inside the silicon. 🔐 wolfCrypt now supports bare-metal STM32 hardware crypto with no STM32 HAL dependency. DHUK and CCB enable device-bound keys that are derived and used in hardware—never exposed to software. Learn more:

wolfssl.comBare-Metal STM32 Hardware Crypto with wolfCrypt: DHUK and CCB Device-Bound Keys - wolfSSLwolfCrypt now drives STM32 on-chip crypto hardware directly from the registers, with zero STMicroelectronics HAL dependency (wolfSSL PR #10395). On top of the

Bring post-quantum signatures to more platforms with fewer dependencies. 🔐 wolfCrypt now includes native Falcon-512 and Falcon-1024, eliminating the liboqs dependency and enabling embedded, Linux kernel, hardware-offload, and verify-only configurations. Learn more:

wolfssl.comwolfCrypt Now Supports Native Falcon anticipating FN-DSA Standardization - wolfSSLwolfCrypt now includes a native implementation of Falcon-512 and Falcon-1024, the lattice-based post-quantum signature algorithm selected by NIST for upcoming

wolfCrypt adds FrodoKEM! 🔐 Looking for a post-quantum key encapsulation mechanism based on unstructured lattices? wolfSSL now supports all 12 FrodoKEM and eFrodoKEM variants, with hardware acceleration and flexible build options. Learn more:

wolfssl.comwolfSSL Adds FrodoKEM Post-Quantum Key Encapsulation - wolfSSLwolfSSL is pleased to announce support for FrodoKEM in wolfCrypt. FrodoKEM joins ML-KEM (FIPS 203), ML-DSA (FIPS 204), LMS/HSS and XMSS/XMSS^MT in our growing

PostgreSQL is being lab validated with wolfProvider to verify operation with wolfCrypt FIPS 140-3. Once validation is complete, PostgreSQL will be able to use FIPS 140-3 validated cryptography through wolfProvider without changes to PostgreSQL itself. Stay tuned for more technical details.