A network stack can compile on a new target and still fail under real traffic. Incorrect DMA ownership, cache handling, locking, or task wakeups can cause dropped packets, corrupted descriptors, and socket calls that never return. This webinar follows the complete wolfIP porting process, from the hardware boundary to blocking BSD-style sockets on an RTOS. […]
Read MoreMore TagMonth: August 2026
liboauth2 is now FIPS 140-3 Tested & Available with wolfCrypt FIPS
liboauth2 is a C library that provides OAuth 2.0 and OpenID Connect functionality for authentication and authorization in applications and web services. FIPS 140-3 support is available for liboauth2 with wolfCrypt FIPS, tested for use with liboauth2 environments. wolfCrypt FIPS provides a lightweight cryptographic module for security focused deployments. This helps organizations secure authentication services […]
Read MoreMore TagBare-Metal STM32 Hardware Crypto with wolfCrypt: DHUK and CCB Device-Bound Keys
wolfCrypt now drives STM32 on-chip crypto hardware directly from the registers, with zero STMicroelectronics HAL dependency (wolfSSL PR #10395). On top of the bare drivers, the port adds DHUK and CCB: chip-bound keys that are derived and used entirely inside the silicon and never appear in software. It is validated across ~27 NUCLEO boards spanning […]
Read MoreMore TagwolfCrypt Now Supports Native Falcon anticipating FN-DSA Standardization
wolfCrypt now includes a native implementation of Falcon-512 and Falcon-1024, the lattice-based post-quantum signature algorithm selected by NIST for upcoming standardization as FN-DSA. The new implementation replaces wolfSSL’s previous liboqs-based Falcon integration. Falcon is now built directly into wolfCrypt, removing the external dependency while improving portability, hardware integration, and control across desktop, embedded, and kernel […]
Read MoreMore TagwolfSSL Adds FrodoKEM Post-Quantum Key Encapsulation
wolfSSL 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 post-quantum portfolio, and it fills a specific gap: a conservative, unstructured-lattice KEM for users who want their quantum-safe key exchange to rest on a different hardness assumption. Why FrodoKEM? ML-KEM is […]
Read MoreMore TagwolfTPM Firmware TPM: Post-Quantum TPM 2.0 (v1.85) on an FPGA Soft-Core
Aerospace, defense, industrial, medical, and energy platforms need a hardware Root of Trust, yet a discrete TPM chip is one more component to procure, qualify, and fit on a board that may run for decades. What if the TPM were simply part of the FPGA you already built? This example runs wolfTPM’s Firmware TPM (fTPM), […]
Read MoreMore TagwolfBoot now uses wolfCOSE for DICE attestation
wolfBoot now uses wolfCOSE as a reusable COSE and CBOR foundation for its existing DICE attestation capability. wolfBoot already provides DICE-based device identity and attestation, and we are now integrating wolfCOSE as the stable, reusable COSE and CBOR layer behind that support. The integration replaces the earlier local token-encoding path with wolfCOSE for creating signed […]
Read MoreMore TagwolfSSL is bringing hardware key isolation to the Altera Agilex 5 SoC FPGA
wolfSSL is adding native support for the Secure Device Manager (SDM) hardened crypto services on Altera Agilex 5 devices. The new port connects wolfCrypt directly to the FPGA Crypto Services (FCS) stack, so keys can live where Linux cannot reach them: inside the SDM itself. Applications get that isolation through the same wolfSSL APIs they […]
Read MoreMore TagwolfCOSE Now Ships as an STM32Cube Pack
wolfCOSE is now available as an STM32Cube pack, I-CUBE-wolfCOSE, so you can add zero-allocation CBOR and COSE to any STM32 project straight from STM32CubeMX or STM32CubeIDE, with no manual source integration. It builds on the wolfSSL Cube pack, I-CUBE-wolfSSL, for all cryptography. What You Get Cube packs let STM32 developers add a library to a […]
Read MoreMore TagwolfSSL vs OpenSSL: Which Fits Your Application?
Should you continue with OpenSSL or migrate to wolfSSL? API compatibility is only the starting point when the library must also fit your target, resource limits, and security requirements. Join this webinar for an engineering comparison of wolfSSL and OpenSSL. See what an OpenSSL 3.x migration involves, where switching makes technical sense, and when remaining […]
Read MoreMore Tag