As of July 31, 2026, the commercial wolfSSL packages and bundled licenses previously provided through Renesas are no longer available for the Renesas RA and RX families or the Renesas Synergy™ Platform. wolfSSL will continue to support Renesas platforms. Developers can license wolfSSL products for Renesas devices directly from wolfSSL. If you previously obtained a […]
Read MoreMore TagCategory: Uncategorized
DTLS 1.3: Securing UDP Connections
UDP moves data with low overhead, but it does not provide encryption. A device’s network address can also change during a session. DTLS 1.3 protects the connection with fewer handshake round trips, explicit acknowledgments, and support for maintaining the session when an endpoint’s address changes. This webinar compares DTLS 1.3 with DTLS 1.2 and follows […]
Read MoreMore TagPQC Update 2026: Standards, Performance, and Migration Reality (APAC-Friendly Time)
Post-quantum cryptography is moving from planning to deployment. With NIST standards finalized, CNSA 2.0 guidance emerging, and hybrid cryptography already appearing in production environments, engineering teams are now facing practical decisions around performance, interoperability, certification, and migration strategy. Join us for a practical update on the PQC landscape in 2026. We’ll review where standards stand […]
Read MoreMore TagPorting wolfIP Anywhere: Writing Device Drivers and Porting to a New OS
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 Tagliboauth2 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 Tag