Post-quantum standards like ML-DSA introduce significant compute challenges. These lattice-based schemes rely on high-degree polynomial math that can overwhelm traditional CPUs, making GPU acceleration essential for high-volume environments. The primary bottlenecks occur during Key Generation and Signing. In ML-DSA, signature generation is particularly intensive due to rejection sampling. This process requires the algorithm to repeatedly […]
Read MoreMore TagCategory: wolfSSL/ wolfCrypt
Idiomatic Zig Bindings for wolfSSL
wolfSSL now has a community-maintained Zig binding—zig-wolfssl—that wraps wolfSSL and wolfCrypt behind a native Zig API. If you are building a Zig application that needs TLS, X.509, or wolfCrypt algorithms, this binding gives you type-safe access without dropping to raw C. New to Zig? Check out the official overview or visit ziglang.org. Getting started with […]
Read MoreMore TagwolfSSL now supports GRPC on Zephyr
The people have been asking for GRPC on Zephyr, and wolfSSL has delivered. We support it with both our FIPS encryption and without FIPS. Contact us at facts@wolfssl.com or call us at +1 425 245 8247 if you have questions about any of the above.
Read MoreMore TagwolfSSL 5.9.1 release blog
wolfSSL 5.9.1 is available with new features, post-quantum cryptography improvements, broad bug fixes, and a number of vulnerability fixes. Users are always recommended to stay up to date with wolfSSL releases. In this release, use cases that are affected by high severity reports are: PKCS7 with ORI callback set or AuthEnvelopedData with AES-GCM (–enable-pkcs7), ECDSA […]
Read MoreMore TagHow Claude Mythos Preview helped harden wolfSSL
At wolfSSL, we do an incredible amount of testing. Some of it is visible, some of it is not. You can see our GitHub Actions run on every pull request, and behind that we have a private Jenkins setup doing more extensive testing across multiple platforms, some of it on hardware physically sat in one […]
Read MoreMore TagAI deluge and wolfSSL average time between Vulnerability Report and Fix
We have always prided ourselves on our mean time between a vulnerability report and delivering a fix. Our historical average is about 36 hours. Like everyone else providing open source infrastructure software, we’ve been under a lot of pressure in the past 30 days with valid and meaningful reports from AI research efforts. Fortunately, we […]
Read MoreMore TagTrue Random vs. Pseudorandom Number Generation
In the world of computing, “randomness” isn’t a one-size-fits-all concept. Whether you are developing a gaming app or securing a high-stakes cryptographic protocol, the type of Random Number Generator (RNG) you choose matters. The distinction boils down to one factor: reproducibility. Download wolfSSL → Pseudorandom Number Generators (PRNGs) A PRNG is a deterministic algorithm. It […]
Read MoreMore TagTLS 1.3 Brainpool Curve Support in wolfSSL
As cryptographic standards and regulatory requirements continue to evolve, the ability to adopt modern security protocols without sacrificing compliance is increasingly important. TLS 1.3 plays a critical role in this evolution — not only as today’s baseline for secure communications but also as the foundation for the ongoing transition toward Post-Quantum Cryptography (PQC). With recent […]
Read MoreMore TagAccelerating ML-DSA Key Generation with wolfSSL and CUDA
With the formalization of ML-DSA for post-quantum usage, lattice-based cryptography introduces a significant compute challenge. Unlike traditional ECC or RSA, ML-DSA relies on complex polynomial math across hundreds of dimensions, creating a performance wall for high-volume systems. To address this compute issue, wolfSSL can utilize CUDA to accelerate these lattice operations, offloading the heavy math […]
Read MoreMore TagWhat wolfSSL supports for RISC-V Users
Core RISC-V Support wolfSSL has no external dependencies and runs on nearly any RISC-V board using standard GNU toolchains. Download wolfSSL → Hardware Platforms Supported A few of the specific boards we currently support: Microchip PolarFire SoC (MPFS250) SiFive HiFive Unleashed (64-bit) SiFive HiFive1 (32-bit E31 RISC-V core at 320MHz with 4MB flash and 16KB […]
Read MoreMore Tag