Latest Posts

• uncategorized

  wolfSSL support for the ATECC608 Crypto Coprocessor

  wolfSSL embedded SSL/TLS support the latest Microchip ATECC508 and ATECC608 I2C cryptographic coprocessors. Prerequisites:

  Read more
• uncategorized

  wolfCrypt FIPS 140-2 on ARM

  Do you need a FIPS 140-2 validated cryptography library for your ARM-based platform? wolfCrypt has been FIPS 140-2 validated (certificate #3389) on several different operating environments to date, some of which have been on resource-constrained ARM-based devices.

  Read more
• uncategorized

  Open Source Project Ports: Socat

  Thanks to the portability of our wolfCrypt library, plus our team of expert engineers, wolfSSL is frequently adding new ports. Keep an eye out as we continue showcasing a few of the latest open source project ports over the next few weeks!

  Read more
• uncategorized

  Post-Quantum wolfSSH

  The wolfSSL library is now safe against the “Harvest Now, Decrypt Later” post-quantum threat model with the addition of our new TLS 1.3 post-quantum groups. But where does that leave wolfSSH? It is still only using RSA and elliptic curve key exchange algorithms which are vulnerable to the threat model...

  Read more
• uncategorized

  Loading wolfSSL into the Linux Kernel - Update

  wolfSSL Linux kernel module support has grown by leaps and bounds, with new support for public key (PK) cryptographic acceleration, FIPS 140-3, accelerated crypto in IRQ handlers, portability improvements, and overall feature completeness.

  Read more
• uncategorized

  wolfSSL not affected by CVE-2021-3711, nor CVE-2021-3712

  It came to our attention that OpenSSL just published two new vulnerabilities.

  Read more
• uncategorized

  wolfCrypt FIPS on EFM32-GG

  A quick followup to the post “wolfSSLs’ Proprietary ACVP client”.

  Read more
• uncategorized

  Post Quantum cURL

  Recently, a lot of post-quantum activity has been happening here at WolfSSL.

  Read more
• uncategorized

  How Much Resource Does Your TLS Take?

  Adding security to a connection comes at a cost. It takes a little time to perform the crypto operations and some memory gets used during the operations. Not all TLS implementations are equal … how much memory and how much time is lost depends on what TLS library is being...

  Read more
• uncategorized

  Hybrid Post Quantum Groups in TLS 1.3

  Recently, we announced our wolfSSL libOQS integration and we said we were planning to hybridize our KEMs with NIST-standardized ECDSA. The hybridization is completed. This is a brief summary of why this matters and what we did.

  Read more