Category: wolfCrypt FIPS

FIPS 140-3 support is coming to pfSense! pfSense is one of the most widely deployed open-source firewall and router platforms in the world, powering everything from small office networks to large enterprise and government deployments. Built on FreeBSD, pfSense has earned a reputation for stability, flexibility, and a rich feature set spanning VPN, IDS/IPS, captive […]

Read MoreMore Tag

In a previous post, we spoke about LMS, XMSS and SLH-DSA in relation to wolfBoot and let you know we’d be bringing some benchmarking numbers. Voila! Algorithm / Parameter Set Sig Size/Strength Verification Time (ms) Operations Per Second LMS/HSS L2_H10_W2 9300 0.118 8500.588 LMS/HSS L2_H10_W4 5076 0.219 4557.764 LMS/HSS L3_H5_W4 7160 0.324 3088.329 LMS/HSS L3_H5_W8 […]

Read MoreMore Tag

Getting FIPS-validated cryptography onto an embedded Linux platform typically involves stitching together kernel modules, userspace libraries, and building system configurations by hand. Now, the meta-wolfssl layer provides a turnkey Yocto build environment that produces a fully integrated wolfSSL FIPS image, from kernel crypto to OpenSSL, GnuTLS, and libgcrypt. You can try it yourself with our […]

Read MoreMore Tag

Your product needs FIPS 140-3. Your stack is Rust. Until now those two facts were in tension. The pure-Rust crypto libraries are not FIPS 140-3 validated. wolfSSL’s Rust crates are different. wolfCrypt has been through FIPS 140-3 validation. The path from Rust to a validated build exists. Here’s what it actually takes. The `fips` feature […]

Read MoreMore Tag

Rust’s crypto ecosystem is good. `ring` is fast and well-tested. RustCrypto covers almost everything. rustls has replaced OpenSSL in a lot of stacks. None of it is FIPS 140-3 certifiable. If you’re shipping to the US federal, healthcare, finance, or defense, that matters. You can write excellent Rust and still get blocked at the compliance […]

Read MoreMore Tag

Does your project require meeting Common Criteria standards? Using wolfSSL’s FIPS-validated module (or FIPS-ready which is tailored towards FIPS requirements) helps a lot with meeting CC (Common Criteria) because it gives strong, reusable evidence for the crypto portion through independent validation of crypto algorithms and validation evidence with ACVP workflows. Having the ACVP tests and […]

Read MoreMore Tag

Medical devices need encryption, but government and healthcare buyers often require FIPS 140-3 validated cryptography to meet compliance standards. wolfCrypt FIPS 140-3 provides validated encryption for embedded medical devices with lower memory and processing requirements than standard crypto libraries. It protects stored data and data in transit. wolfSSL FIPS extends this validation to TLS connections […]

Read MoreMore Tag

We’re looking at building a wolfCrypt backend for OpenZFS native encryption. Before we commit, we want to know who needs it. If you’re running encrypted ZFS datasets, you’re running unvalidated crypto that no FIPS module can currently help with. Nobody offers FIPS-validated ZFS encryption. Anywhere. The engineering is straightforward. We have already spec’d and prototyped […]

Read MoreMore Tag

We’re looking at bringing FIPS 140-3 validated cryptography to Proxmox VE. Before we commit, we want to know if the market actually wants it. Here’s the situation. Broadcom’s VMware licensing changes are pushing a lot of enterprise customers toward Proxmox. Proxmox is solid (Debian-based, KVM, mature, production-proven) and the migration makes technical sense. But organizations […]

Read MoreMore Tag