So, what’s new at wolfSSL? Take a look below to check out the most recent news.
Or sign up to receive weekly email notifications containing the latest news from wolfSSL.
In addition, wolfSSL now has a support-specific blog page dedicated to answering some of the more commonly received support questions.

wolfSSL Asynchronous Release v4.4.0

The wolfSSL / wolfCrypt libraries support asynchronous (non-blocking) crypto using hardware acceleration with the Intel QuickAssist and Cavium Nitrox III/V adapters. These are PCIe devices that accelerate crypto operations. For server platforms requiring high connection rates and throughput this allows greatly increased performance.

For some performance numbers see this page:

Release v4.4.0 of wolfSSL Async has bug fixes and new features including:

  • All wolfSSL v4.4.0 release fixes (
  • Fix for uninitialized `supSha3` warning.
  • Fix for use of incorrect devId for wolfSSL_SHA3_256_Init.
  • Fix for QAT with Shake256.
  • Fix for QAT example `./`.

To find out more or get an evaluation please email

wolfBoot 1.5 Release

wolfBoot version 1.5 has been released and can be downloaded from our website. New features that are available starting from this release include:

  • Support for SHA-3 digest for firmware images
  • Support for RSA-4096 signature authentication
  • Support for a new architecture (ARMv8 64bit)
  • Support for new targets and platforms (LPC54xx, raspberry pi, Xilinx Zynq)
  • Improved experience for development in MS Windows environments
  • Virtual storage over UART

wolfBoot is now capable of securing the boot process in embedded Linux systems based on the ARM Cortex-A CPU. wolfBoot integrates with your platform chain-of-trust, adding support for reliable and trusted
firmware updates. All the execution levels on systems using ARM TrustZone to separate privileges among boot stages are supported in the new boot procedure.

Using wolfBoot 1.5 it is now possible to set up a virtual update partition on a neighbor system, which can be accessed using UART. Example code is provided to demonstrate this feature.

The developer experience in windows environments has been improved by adding official support for IAR and integrating a Visual Studio solution to facilitate the compilation and the integration of key management tools. Integrating secure boot in your embedded systems has never been this easy.

Check out our release notes for more details, and feel free to contact us at with any questions.

wolfSSH 1.4.4 Now Available

wolfSSL Inc is proud to announce the release of wolfSSH v1.4.4, the embedded SSH library for devices, IoT, and the cloud. Included in the release are:

  • wolfSCP client. Included now is an example SCP client tool, wolfSCP. It can be used to copy single files or directories between two endpoints.
  • VxWorks support. wolfSSH may now be compiled to run on the VxWorks RTOS from Wind River Systems. It doesn’t require any special configuration, just compile and go.

Contact us at with any questions about using new features available in the wolfSSH embedded SSH library!  Download the new release today from the wolfSSL download page or direct from GitHub.

wolfTPM v1.8 Release

wolfTPM Version 1.8 has been released and is now available for download on our website. This release brings new platform support for Xilinx Zynq UltraScale+ MPSoC and new operating environment support for Linux users. We have now tested with two more TPM modules, the Nuvoton NPCT650 and NationsTech Z32H330.

To reduce the time needed for new applications on Linux we’ve added support for the Linux TIS kernel driver (“/dev/tpm#”). This allows applications using wolfTPM under Linux to exist alongside the Linux TPM tools. It also makes it easier for users to leverage existing Linux TPM module and LPC bus support without the need for additional system configuration.

The default build-behavior is to use the “/dev/spidev#.#” directly via the HAL IO callback. To enable the “/dev/tpm#” support use the “./configure –enable-devtpm” build option.

This release also resolves some build issues with the crypto callback support for TLS and adds examples for using an ECC primary storage root key.

For questions please email

wolfSSL Support for the Deos Safety Critical RTOS

Are you a user of Deos?  If so, you will be happy to know that wolfSSL supports the Deos RTOS and has added TLS client/server examples to the wolfSSL embedded SSL/TLS library for Deos!

Deos is an embedded RTOS used for safety-critical avionics applications on commercial and military aircraft. Certified to DO-178C DAL A, the time and space partitioned RTOS features deterministic real-time response and employs patented “slack scheduling” to deliver higher CPU utilization. DO-178C DAL A refers to a specification that is required for software to be used in aerospace software systems. 

The Deos port in wolfSSL is activated by using the "WOLFSSL_DEOS" macro. For instructions on how to build and run the examples on your projects, please see the “<wolfssl-root>/IDE/ECLIPSE/DEOS/README” file. 

wolfSSL provides support for the latest and greatest version of the TLS protocol, TLS 1.3! Using the wolfSSL port with your device running Deos will allow your device to connect to the internet in one of the most secure ways possible.

For more information, please contact

The most recent version of wolfSSL can be downloaded from our download page, here:
wolfSSL GitHub repository:
wolfSSL support for TLS 1.3:
Deos RTOS homepage:

wolfSSL FIPS Ready 4.4.0 Now Available!

Do you have a product you are working on that may one day be utilized by a government agency either foreign or domestic or any agency that requires a FIPS certification? If you think your product is a candidate for FIPS use but are not quite sure when you may have a FIPS purchase come through wolfSSL FIPS Ready is exactly what you are looking for!

What is FIPS Ready?

wolfSSL FIPS Ready is the wolfCrypt FIPS enabled cryptography layer code included in the wolfSSL source tree. With wolfSSL FIPS Ready you get to benefit from all the enhanced security features that come with a FIPS module but you don’t have to get a certificate until you are confident you have a FIPS customer that will justify the effort of getting the cert!

What are the Limitations?

With wolfSSL FIPS Ready you are not FIPS approved, but you will be READY to get approved at a moments’ notice saving you time when that FIPS customer comes knocking. Being FIPS Ready means you have included the FIPS code in your build, you are already operating according to the FIPS enforced best practices of default entry point, you have a code integrity check of your crypto module and you are running the power on self test to ensure proper cryptographic functionality. When the time comes, you can get your operating environment tested and validated and all the coding work will have already been done in advance making the validation process much faster!

Can I deploy it today?

FIPS Ready is open source and dual-licensed. We distribute FIPS Ready wolfSSL with the GPLv3 license or we can negotiate commercial licensing terms with support!

You can download a copy of the from the DOWNLOADS page on the wolfSSL website.

FIPS is a complicated topic so if you have questions after reviewing this post, then just contact us at anytime, we are always happy to help in any way we can!

wolfMQTT Release 1.6.0

The team at wolfSSL is proud to announce the latest iteration of wolfMQTT. This release is focused on polishing the user experience and squashing bugs. The multithread feature was thoroughly tested, and we managed to correct a couple of synchronization issues that were reported. Additionally a new “simple client” example was added that demonstrates the bare-bones essential API needed to allow an IoT device to communicate with a broker service.

Check out the changelog here:

While you’re there, show us some love and give the wolfMQTT project a Star!
You can download the latest release here:
Or clone directly from our GitHub repository:

To learn more about wolfMQTT, the wolfSSL embedded SSL/TLS library, or one of our other products, contact us today at

Netflix leverages TLS 1.3 for safer and faster streaming experiences

The Netflix Tech Blog recently shared how Netflix is leveraging TLS 1.3 for faster and more secure connections.  They concluded:

“From the security analysis, we are confident that TLS 1.3 improves communication security over TLS 1.2. From the field test, we are confident that TLS 1.3 provides us a better streaming experience.

At the time of writing this article, the Internet is experiencing higher than usual traffic and congestion. We believe saving even small amounts of data and round trips can be meaningful and even better if it also provides a more secure and efficient streaming experience.

Therefore, we have started deploying TLS 1.3 on newer consumer electronics devices and we are expecting even more devices to be deployed with TLS 1.3 capability in the near future.”

The wolfSSL embedded SSL/TLS library was one of the first TLS libraries to implement support for TLS 1.3, and we are happy to see successful adoption stories like this!  Contact us at to start using TLS 1.3 in your projects!

Initial MQTT Support in cURL, send us Feedback!

Earlier this month, we worked on adding MQTT support to cURL which is now available as “experimental” in the latest curl 7.70.0 release! For full details of the current integration, see Daniel Stenberg’s blog post titled “CURL + MQTT = TRUE“.

We’re curious how our users want to use MQTT in cURL, and we want to hear your feedback to help direct our future cURL+MQTT plans! We think MQTT support could be helpful for a variety of use cases ranging from service techs that require a tool to help test and develop MQTT-based solutions, to easily scripting MQTT commands. Let us know your feedback at and we’ll be happy to listen!

New Features in the wolfSSL 4.4.0 Release

wolfSSL Inc is proud to announce the release of wolfSSL v4.4.0, the embedded TLS library for devices, IoT, and the cloud. Included in the release are:

  • Qualcomm Hexagon SDK support. The Hexagon SDK is used for building code to run on DSP processors. Use of the Hexagon toolchain to offload ECC verify operations has been added to wolfSSL. This can free up the main CPU for other operations or lead to future optimizations with HVX on some algorithms that use vector operations. The Makefile for building with the Hexagon toolchain and a README with more information can be found in the directory wolfssl-4.4.0/IDE/HEXAGON.
  • Apache 2.4.39 support. Use wolfSSL with Apache’s mod_ssl. Apache is the most commonly used web server in the world. You can now use wolfSSL as a part of your Apache installation. You can benefit from wolfSSL’s world class support. Ask us for more information.
  • OpenVPN support. Use wolfSSL with OpenVPN. OpenVPN is one of the top VPN products on the market. wolfSSL can secure your connections.
  • Renesas Synergy S7G2 support. Are you prototyping a new embedded application with a Renesas Synergy S7G2 board? wolfCrypt can take advantage of its on-board cryptography hardware. Offload AES, RSA, SHA, and GHASH to the hardware. See our benchmarks page to see the comparison of the software crypto and the hardware acceleration.
  • Curve448, X448, and Ed448 support. We at wolfSSL like to stay on top of progressive ciphers. Curve448 is an efficient to calculate elliptic curve. It offers 224-bits of security and works well with ECDH key agreement.

Contact us at with any questions about using new features available in the wolfSSL embedded SSL/TLS library!

Posts navigation

1 2 3 4 5 6 7 114 115 116

Weekly updates


Latest Tweets