The security of wolfSSL products is always on our mind and holds high importance. Conducting regular, diligent, and well-planned testing helps maintain wolfSSL’s robustness and security. We strive to write and maintain clean, readable, and understandable code. Like the halting problem, we know it is impossible to test every single possible path through the software, but […]
Read MoreMore TagCategory: Uncategorized
wolfSSL STM32F7 Support
We would like to announce that the wolfSSL embedded SSL library now has support for hardware-based cryptography and random number generation offered by the STM32F7. Supported cryptographic algorithms include AES (CBC, CTR), DES (ECB, CBC), 3DES, MD5, and SHA1. For details regarding the STM32F7 crypto and hash processors, please see the STM32F7 Hardware Abstraction Layer (HAL) and […]
Read MoreMore TagwolfSSL with PikeOS and ElinOS and TLS 1.3
Are you a user of PikeOS or ElinOS, and interested in a lightweight TLS 1.3 implementation? The wolfSSL embedded SSL/TLS library now supports TLS 1.3 (drafts 18 and 20). TLS 1.3 improves performance of establishing TLS connections by reducing the required number of round trips during the TLS handshake (including a new 0-RTT option where applications can […]
Read MoreMore TagNXP CAU, mmCAU, and LTC Hardware Cryptography with TLS 1.3
As you may know, wolfSSL includes support for offloading cryptography operations into NXP Coldfire and Kinetis devices that include the CAU, mmCAU, or LTC hardware crypto modules. Taking advantage of these modules improves performance of both the cryptography and the SSL/TLS layer running on top of it. Here is a quick comparison of performance between […]
Read MoreMore TagMicrochip PIC32MZ with TLS 1.3
As you may know, wolfSSL includes support for offloading cryptography operations into the PIC32MZ hardware crypto module. This improves performance of both the cryptography and the SSL/TLS layer running on top of it. Here is a quick comparison of performance between software cryptography and the hardware-based cryptography offered by the PIC32MZ: Software Crypto Hardware […]
Read MoreMore TagwolfSSL Package for Arch Linux
Hi! Are you a user of Arch Linux? wolfSSL 3.12.0 is now available as a package in the Arch User Repository! https://aur.archlinux.org/packages/wolfssl wolfSSL, written in C, supports industry protocol standards up to TLS 1.3 and DTLS 1.2 and progressive ciphers including ChaCha20, Poly1305, Curve25519, Ed25519, and SHA-3. We encourage you to give our package a try and let […]
Read MoreMore TagwolfSSL FIPS with Intel® SGX
wolfSSL supports use with Intel® SGX on both Windows and Linux. In addition to being available on both operating systems the Linux example includes running a full TLS connection in a secure Enclave. Examples can be found on GitHub under wolfssl/wolfssl-examples located here (https://github.com/wolfSSL/wolfssl-examples). One of the exciting upcoming features this year, is that wolfSSL […]
Read MoreMore TagwolfCrypt 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 on several different operating environments to date, some of which have been on resource-constrained ARM-based devices. FIPS validating a crypto library on a resource-constrained device can be more involved than doing a validation on a standard […]
Read MoreMore TagwolfSSL FIPS – A Year in Review (Part 2 of a 3 Part Series)
Greetings! In this post we are covering Operational Environment’s (OE’s) we worked with this past year. These OE’s were validated under an OEM relationship where the company validating is licensed to resell the wolfCrypt FIPS product under their own brand name. wolfSSL was particularly excited about both of these projects as they display the great […]
Read MoreMore TagwolfSSL 3.12.0 Now Available
wolfSSL 3.12.0 is now available for download! This release contains bug fixes, new features, and includes fixes for one security vulnerability (low level). The one low level vulnerability fix included in this release is in relation to a potential DoS attack on a wolfSSL client. Previously a client would accept many warning alert messages without […]
Read MoreMore Tag