Actually, no. We are not going to add another entry into our product portfolio called wolfCaliptra. There are already so many! Caliptra defines a module that includes specifications for hardware and software. To be honest, wolfSSL is a software organization, so something that would be called wolfCaliptra would fall outside the scope of what we […]
Read MoreMore TagMonth: May 2026
wolfHSM and Concurrency
Systems that integrate an HSM often have multiple threads or subsystems performing cryptographic operations at the same time. wolfHSM is designed to support this kind of workload while keeping the request/response protocol simple and predictable. wolfHSM concurrency is primarily achieved by the server processing requests from multiple client sessions in parallel. Each session processes requests […]
Read MoreMore TagwolfBoot Port for NXP T2080 QorIQ for Avionics
wolfSSL is pleased to announce wolfBoot support for the NXP QorIQ T2080, a quad-core Power Architecture e6500 processor used in aerospace, defense, and industrial control. wolfBoot is a compact, portable secure bootloader that replaces U-Boot with cryptographic firmware verification and optional Post-Quantum Cryptography (PQC) – pure PQC or hybrid classical/PQC. It compiles to under 32 […]
Read MoreMore TagDifference between TLS Session ID and Tickets
TLS session resumption reuses previously negotiated keying material to shorten handshakes and reduce CPU and network overhead. Resumption saves latency and power on constrained devices by avoiding a full handshake when a safe cached session is available.—–Understanding Session IDs and Tickets Session IDs are a server-issued identifier used by TLS ≤ 1.2 where the server […]
Read MoreMore TagHow to Leverage FIPS to Meet Common Criteria Requirements
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 TagStopping Ransomware at the Device Level
Ransomware now targets medical devices, not just IT systems. Once malicious code runs on a device, it can disrupt patient care. The best defense is preventing execution. wolfSSL blocks ransomware before it runs: wolfBoot – Prevents unauthorized firmware from executing at startup wolfCrypt – Encrypts storage and secures firmware updates to prevent tampering wolfSentry – […]
Read MoreMore TagFIPS 140-3 Encryption for Connected Medical Devices
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 TagWhy Secure Boot Is Now an FDA Expectation
The FDA now expects medical devices to use a secure boot. Without it, devices can run unauthorized firmware, including malware or compromised code from supply chain attacks. wolfBoot is a secure bootloader for embedded medical devices. It uses wolfCrypt to verify firmware signatures before allowing code to run. Only authenticated firmware executes. For additional security: […]
Read MoreMore TagSecuring Medical Devices From Device to Cloud
Medical devices send patient data from bedside monitors and wearables to cloud systems. That data needs protection at every step. wolfSSL secures the full path: wolfSSL/wolfCrypt – Encrypted communication ((D)TLS 1.3) between devices and servers wolfMQTT – Secure messaging for device-to-cloud data transfer wolfSSH – Encrypted remote access for maintenance and diagnostics wolfTPM – Hardware […]
Read MoreMore TagFIPS 140-3 Validated OpenZFS Encryption: Is There Demand?
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