Our wolfSSL library has several post-quantum algorithms built in, but on their own, they aren’t always useful. How else can the PQC algorithms be used in production? Well, one of our areas of expertise is getting other open-source projects working with wolfSSL and then getting those integrations using post-quantum algorithms. We have post-quantum integrations with […]
Read MoreMore TagCategory: wolfSSL/ wolfCrypt
MAX32666 and MAX32665 Hardware Acceleration added to wolfSSL
wolfSSL now supports using the Trust Protection Unit (TPU), Modular Arithmetic Accelerator (MAA), and TRNG provided by Analog Devices MAX32666 and MAX32665 microcontrollers. The implementation can be seen in PR #7777 to wolfSSL, and is in wolfSSL starting at 5.7.4! The port offers various usage options: fully leveraging all hardware features, selectively enabling specific hardware […]
Read MoreMore TagX509 Attribute Certificate support
wolfSSL is adding support for X509 Attribute Certificates (ACERTs, for short), enabled with –enable-acert. This initial support includes reading, printing, and verifying. Furthermore, it uses our new ASN.1 template implementation, and supports RSA-PSS as well. But what is an X509 Attribute Certificate, and how does it differ from the more commonly encountered X509 Public Key […]
Read MoreMore TagLMS in PKCS11
Most people know that wolfSSL supports being a PKCS11 consumer. It is easy to enable this with the –enable-pkcs11 configure time flag and then trying out the examples. Now, what most people don’t realize is that we also have the ability to be a PKCS11 provider!! This is via our library called wolfPKCS11. Check out […]
Read MoreMore TagwolfSSL 5.7.4 Release
wolfSSL release 5.7.4 is now available, with exciting optimizations for ARM devices and enhancements to post-quantum cryptography algorithms. If you’re using wolfSSL on RISC-V, we’ve also included new performance enhancements specifically for RISC-V devices. Alongside these optimizations and new features, several important fixes were made. One notable fix involves the behavior of X509_STORE_add_cert() and X509_STORE_load_locations() […]
Read MoreMore TagwolfSSL wolfCrypt CSharp wrapper
wolfSSL is excited to announce additional support for wolfCrypt API’s in our CSharp (C#) wrapper. Our CSharp wrapper now includes wolfCrypt support for ECC (ECDSA/ECDHE), ECIES, RSA, ED25519/Curve25519, AES-GCM, and HASH cryptographic algorithms. The supported HASH algorithms are MD2, MD4, MD5, SHA, SHA-224, SHA-256, SHA-384, SHA-512, SHA-MD5, SHA3-224, SHA3-256, SHA3-384, SHA3-512, BLAKE2B, and BLAKE2S. In […]
Read MoreMore TagEnhance Embedded System Security with ADI MAXQ1065 and wolfSSL
wolfSSL’s trusted partner, Analog Devices, Inc. (ADI), recently announced that integrating the MAXQ1065 with wolfSSL can significantly enhance security for IoT and embedded systems. Explore the ADI Engineer Zone blog post, Securing IoT and Embedded Systems: Integrate MAXQ1065 with wolfSSL, to discover wolfSSL’s competitive advantages and how this integration improves IoT security solutions and embedded […]
Read MoreMore TagDeprecation and Removal of TLS 1.0 / 1.1 Support from wolfSSL
As part of our quality control and review process, wolfSSL is planning removal of obsolete and deprecated TLS protocol support from our mainline TLS library. TLS 1.0 and 1.1 were introduced in 1999 and 2006 respectively, and both versions were formally deprecated by RFC 8996 in 2021. As noted in the deprecation RFC, TLS 1.0 […]
Read MoreMore TagIntroducing rustls-wolfcrypt-provider: wolfCrypt for Rustls
rustls-wolfcrypt-provider integrates the wolfCrypt cryptographic library as a backend for Rustls, allowing developers to use wolfCrypt’s secure cryptographic functions with Rustls’ modern TLS stack. Currently in alpha, this library offers flexibility for those needing an alternative crypto provider, especially for projects requiring FIPS 140-3 readiness. Other reasons to consider wolfCrypt as your Rustls provider include […]
Read MoreMore TagStrengthening RSA default minimum to 2048 bits
wolfSSL helps make the internet secure. Part of this task is continually updating our default settings to keep up with adversarial advancements. A recent article detailed the use of default RSA key sizes by an IoT manufacturer, which resulted in a 512 bit key being used for authentication. “The factoring required $70 in cloud computing […]
Read MoreMore Tag