Dynamic memory can make embedded networking unpredictable. Heap fragmentation can cause allocation failures, while non-deterministic allocation times can interfere with real-time deadlines. Memory corruption and undefined behavior make these failures even harder to reproduce and diagnose. Join us on September 30 at 8 AM PT for this dynamic and informative webinar. wolfIP addresses these challenges […]
Read MoreMore TagCategory: Uncategorized
Live Webinar: Preparing Connected Devices for the EU Cyber Resilience Act (EU-Friendly Time)
The EU Cyber Resilience Act (CRA) establishes cybersecurity requirements for products with digital elements sold in the EU. These requirements affect how connected and embedded products are designed, secured, updated, documented, and maintained throughout their lifecycle. As CRA implementation progresses, engineering and product teams need to stay informed about the latest requirements, timelines, and compliance […]
Read MoreMore TagHigh-Entropy Random Numbers from Oscillator Jitter on C2000 C28x
The LAUNCHXL-F28P55X (TMS320F28P550SJ) features a 150 MHz C28x DSP from TI’s C2000 real-time control family. Designed for motor drives, solar inverters, EV chargers, and digital power supplies, it lacks a hardware TRNG. However, it provides three independent clock sources: two on-chip RC oscillators (INTOSC1 and INTOSC2) and the crystal driving the PLL. Using the chip’s […]
Read MoreMore TagwolfCOSE Adds PSA Attestation and EAT Support
wolfSSL is adding PSA Initial Attestation API 2.0 and RFC 9783 PSA Entity Attestation Token (EAT) support to wolfCOSE. This lets a device prove its identity, security lifecycle state, and boot measurements to a relying party using the compact COSE/CBOR formats already used across the IoT ecosystem. Consistent with wolfCOSE’s design, PSA/EAT is fully off […]
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 TagwolfCOSE Adds COSE Countersignatures
wolfSSL is adding RFC 9338 COSE Countersignature support to wolfCOSE, letting a second party sign over an already-signed, encrypted, or MAC’d COSE message. Countersignatures matter for notarization, timestamping, and multi-party workflows, proving that a message existed and was endorsed by an additional authority after the fact, and making wolfCOSE a fit for supply-chain and attestation […]
Read MoreMore TagWhat We’ve Been Building: A wolfMQTT Update
Since the wolfMQTT 2.1.0 release back in July, the team has been busy working on some major upgrades. Whether you’re running a client or a broker, there’s a lot to dig into in the current master branch on GitHub. We’ve focused on smoothing out the developer experience, tightening up protocol compliance, and, most importantly, a […]
Read MoreMore TagBringing wolfSSL in line with RFC 9846
RFC 9846, published in July 2026, obsoletes RFC 8446 as the specification for TLS 1.3. It is a minor revision in that it is backward compatible, but it tightens a number of requirements that were previously advisory. At wolfSSL, we are working hard on implementing the specification. No KeyUpdate while sending early data. Section 5.5 […]
Read MoreMore TagOpenBao FIPS 140-3 Support with wolfProvider
OpenBao is an open-source secrets management platform used to store, manage, and distribute credentials, encryption keys, and certificates. wolfSSL is evaluating OpenBao with wolfProvider to verify operation with wolfCrypt FIPS. OpenBao can use FIPS 140-3 validated cryptography through wolfProvider with no code changes to OpenBao and potentially no code changes to applications using it, provided […]
Read MoreMore TagwolfBoot now supports booting FAT32 and ext4 Filesystems
wolfBoot can now read a signed firmware image from a file on a filesystem. This applies to the disk boot path, which covers SD cards, eMMC, SATA and NVMe targets. The feature is read only, optional, and off by default. What it does wolfBoot has supported MBR and GPT partition tables on disk targets for […]
Read MoreMore Tag