wolfSSL was OpenWrt’s default TLS library from the 21.02 release until 23.05, when OpenWrt switched to Mbed TLS. One of the reasons given was that Mbed TLS is “considerably smaller”. In part one, I compared wolfSSL, Mbed TLS and OpenSSL on a 650 MHz MIPS router. There, the wolfSSL image came out within 13 KB […]
Read MoreMore TagCategory: wolfSSL/ wolfCrypt
OpenWrt on wolfSSL, Part 1: How It Stacks Up on a MIPS Router
OpenWrt is the Linux distribution behind a huge number of home routers, access points and small embedded boards. wolfSSL was its default TLS library from the 21.02 release until 23.05, when OpenWrt switched to Mbed TLS. One of the reasons given was that Mbed TLS is “considerably smaller”. A lot has changed in wolfSSL since […]
Read MoreMore TagBuilding Secure Embedded Systems with wolfSSL and IAR
In the aerospace and defense (A&D) sectors, security, performance, and deterministic assurance are mission-critical. And as various industries prepare for the Post-Quantum Cryptography transition, embedded developers need development tools and security libraries that don’t compromise on constrained system resources. wolfSSL and IAR provide a proven complementary solution that combines an optimized embedded toolchain with lightweight, […]
Read MoreMore TagHardware AES for wolfCrypt on the TI C2000 C28x
The TI C2000 family is TI’s real-time control line: the MCUs inside motor drives, solar inverters, EV chargers and digital power supplies. wolfCrypt now drives the hardware AES accelerator on the LAUNCHXL-F28P55X (TMS320F28P550SJ), a 150 MHz C28x DSP with 133 KB RAM and 1088 KB flash. The F28P550SJ carries an on-chip AESA block, a TI […]
Read MoreMore TagVorago VA416x0 Hardware TRNG Support in wolfCrypt
The Vorago VA416x0 is a radiation-hardened Arm Cortex-M4F microcontroller used in space, satellite and other high-reliability systems, and is fully supported by wolfSSL and wolfBoot. wolfCrypt now adds support for its on-chip True Random Number Generator (TRNG), a hardware entropy source for TLS and key generation. Enable with WOLFSSL_VA416X0_TRNG and the Vorago SDK header va416xx.h […]
Read MoreMore TagwolfSSL on NetX Duo: DTLS over UDP and Dependable Non-Blocking I/O in 5.9.4
wolfSSL has run on ThreadX and NetX for over a decade, and release 5.9.4 makes that integration noticeably better: NetX sockets now carry DTLS over UDP, and the NetX I/O layer reports “would block” and “connection closed” the way wolfSSL expects, so non-blocking applications work as designed. What’s new in wolfSSL 5.9.4 Two changes in […]
Read MoreMore TagPKCS#7 and CMS in wolfSSL: Hardened, Interoperable and Ready for Enrollment
PKCS#7 and CMS sit underneath signed firmware, S/MIME, signed SBOMs and certificate enrollment with SCEP and EST. Over the past months we reworked large parts of the PKCS#7 code in wolfCrypt with one goal: decode what other implementations actually send, encode what enrollment servers need, and fail loudly instead of quietly. Below is a summary […]
Read MoreMore TagVerify Your wolfSSL Build with OmniBOR and make bomsh
An SBOM says which wolfSSL you ship. make bomsh shows how that binary was built. Install python3, pyspdxtools (pip install spdx-tools), bomtrace3, and bomsh_create_bom.py before you run configure. configure records their paths. bomsh_sbom.py is optional. ./configure && make bomsh The target does a clean rebuild of wolfSSL under bomtrace3, a patched strace from the OmniBOR […]
Read MoreMore TagwolfSSL 5.9.4 Introduces Automated SBOM Generation for CRA Compliance
SBOM instructions on GitHub wolfSSL 5.9.4 writes its own Software Bill of Materials. After a normal build, run: ./configure && make && make sbom It needs python3 and pyspdxtools (pip install spdx-tools) installed before you run configure. make sbom stages a private install, hashes the installed library, and reads the build macros from the configured […]
Read MoreMore TagReducing Yocto and OpenWRT RAM Usage by Switching from OpenSSL to wolfSSL
On Yocto Linux Scarthgap, the wolfSSL endpoint process peaks at 10–13 KB of heap + stack, compared with 750–790 KB for OpenSSL, for an ECDHE P-256 / ECDSA P-256 / AES-128-GCM connection. These figures apply in both directions and to both TLS 1.2 and TLS 1.3. On OpenWRT using uclient-fetch to grab 100k of data, […]
Read MoreMore Tag
