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. wolfSSL also has a support-specific blog page dedicated to answering some of the more commonly received support questions.

Experimental support for realm

Looking to add FIPS-certified crypto to your Realm database app? WolfSSL can help!

We are working on getting wolfSSL upstreamed into Realm as a TLS and crypto provider, and can provide a preliminary version tested on Linux for interested customers. We can also work with you to get other platforms like Android and iOS supported by request.

If you want your Realm database to harness the power and security of wolfSSL, please reach out to us and let us know!

As always, if you have questions on any of the above, please contact us at, or call us at +1 425 245 8247.

Download wolfSSL

Static library framework for Apple devices

We’ve got an exciting new update for our Apple ecosystem support! wolfSSL now contains a script that automates building and packaging wolfSSL static libraries as an XCFramework that can run on all Apple platforms and targets, further simplifying integration into your Xcode projects.

Instead of manually adding all wolfSSL source files to your Xcode project and having to use a user_settings.h file, you can now simply run the script with your desired configure options to build and package wolfSSL, and then drag-and-drop the imported framework bundle into XCode. The framework bundle contains wolfSSL static libraries targeting all modern Apple platforms and simulators. This includes MacOS (arm64, x86_64), iPhone (arm64), iPhoneSimulator (arm64, x86_64), appleTV (arm64), appleTVSimulator (arm64, x86_64), appleWatch (arm64), and appleWatchSimulator (arm64, x86_64). We also include a new “wolfssl-multiplatform” demo application in Xcode demonstrating how a swift application can use a “bridging header” to call into C code and use wolfSSL.

You can find the new build utilities and the “wolfssl-multiplatform” example app in the wolfSSL source tree at IDE/apple-universal. Check out the README to get started. Integrating wolfSSL to your Xcode project has never been easier!

As always, if you have questions on any of the above, please contact us at, or call us at +1 425 245 8247.

Download wolfSSL

Keystores and Secure Elements supported by wolfSSL

When looking to store your cryptographic secrets, it is important to have a good platform to store them on. Even more important is the ease of accessing and using those secrets. Through wolfTPM, we have already added support for the following platforms:

  • Raspberry Pi (Linux)
  • MMIO
  • STM32 with CubeMX
  • Atmel ASF
  • Xilinx
  • QNX Infineon TriCore and Barebox

Testing done using the following TPM (Trusted Platform Module) 2.0 modules:

  • Infineon OPTIGA SLB9670/SLB9672
  • Microchip ATTPM20
  • Nations Tech Z32H330TC
  • Nuvoton NPCT650/NPCT750

For direct Secure Element access, we also have ports in wolfSSL for:

For more detailed information on our supported hardware take a look at We also offer support for PKCS11 to interface to various HSMs.

Another product of interest could be wolfBoot, which – as the name suggests – is a bootloader that can use an HSM (Hardware Security Module) for validation and verification. It supports use of the ARM TrustZone technology. WolfBoot can also be used in an fTPM (Firmware TPM) environment.

Questions? Please feel free to contact out to us as, call us at +1 425 245 8247, or view our FAQ page.

Download wolfSSL

How and why to use ECH (Encrypted Client Hello)

In early 2023 wolfSSL added support for the Encrypted Client Hello draft extension for TLS 1.3 (formerly known as Encrypted Server Name Indication(ESNI)). The Encrypted Client Hello (ECH) extension encrypts the client_hello message meant for a TLS 1.3 server and sends it as an extension of an outer client_hello that has the sensitive fields removed. This encryption obfuscates the sensitive parts of the client_hello (such as the Server Name Indication (SNI)) from any passive observer that may capture the client_hello.

Why use ECH?

Data in the client hello can be used to identify which site a client is trying to access behind a reverse proxy, which may be used to track the user across the internet or disrupt a reverse proxy by identifying the number of servers active or where the server may be geographically. If you would like more detailed information on ECH, check out the draft extension and for more information on reverse proxies checkout Cloudflare’s article on proxies.

We recently added a new example of how to set up our TLS 1.3 server to use ECH, available at along with an example client that will set the ECH configs out of band and then connect to it When the server starts it creates ech-configs, which are a list of Hybrid Public Key Encryption (HPKE) keys and server names that the server will accept for an ECH connection. Once the configs are generated they can be shared out of band with the client or can be obtained through the retry-configs method by connecting and disconnecting the client with a GREASE ECH. In this example the server will print out the base64 encoded configs that can then be passed to the example client as a command line argument and it will load the configs and use them for ECH. In a typical real world application the ECH configs would be published as a DNS record that the client’s web server fetches but that is outside the scope of wolfSSL.

For more information on HPKE check out our blog post. For an example of how to obtain ECH configs through the retry-configs method, check out our other ECH example. If you have questions on any of the above, please contact us at, or call us at +1 425 245 8247.

Download wolfSSL

wolfSSHd Works on Windows!

Did you know that the recent SSHd addition to wolfSSH has also been ported over to Windows? It can run as a service and host incoming SSH, SFTP, and SCP connections. This took some effort in the engineering department here at wolfSSL. Getting interop with clients using Linux terminals streamlined and porting over the wolfSSHd authentication methods. All of this is taken care of in the background making it easy to get up and running. Making use of wolfSSH also gains the advantage of post quantum support along with the cryptographic library wolfCrypt. Additionally providing the capability to be FIPS certified! For more information about using wolfSSHd on Windows contact, or call us at +1 425 245 8247.

Download wolfSSL

How to build a smaller wolfSSL library when used with cURL?

The size of software builds can often be a concern for developers, particularly in embedded systems or other resource-constrained environments. Recently, a change was made to the wolfSSL library that has resulted in smaller build sizes when used with the popular cURL library.
When building wolfSSL, this recent change removes the need for using


instead only requires

–enable-opensslextra=x509small CPPFLAGS=-DHAVE_CURL

This compiles out a lot of compatibility layer functionality (used for ripping out and replacing OpenSSL) that is not needed by cURL. This change can be especially beneficial in resource-constrained environments where smaller builds are crucial. Find more information about using wolfSSL with cURL or about the even smaller tiny-curl. If you have questions on any of the above, please contact us at, or call us at +1 425 245 8247.

Download wolfSSL

What Operating Systems has wolfSSL been ported to?

When embarking on a project the operating system used is a hard choice and limiting factor. Many embedded IoT projects even do without the operating system due to resource constraints. wolfSSL is a compact, highly customizable, and open-source SSL/TLS library that provides encryption, authentication, and secure communication. One remarkable feature, among many, of wolfSSL is its versatility – it has been ported to a large selection of operating systems, enabling developers to integrate robust security into a diverse range of platforms.

Ported operating systems range all the way from the obvious and expected operating systems to embedded and niche operating system:

  1. Linux (embedded Linux, Yocto Linux, PetaLinux, Debian, and more)
  2. Windows
  3. MacOS
  4. FreeBSD, NetBSD, OpenBSD
  5. Android
  6. iOS
  7. QNX
  8. FreeRTOS, SafeRTOS
  9. VxWorks
  10. GreenHills INTEGRITY
  11. ThreadX
  12. WinCE
  13. TRON
  14. Micrium
  15. MQX
  16. embOS
  18. RIOT
  20. TinyOS
  21. Nucleus
  22. Solaris
  23. OpenWRT
  24. TI-RTOS
  25. Keil RTX
  26. MontaVista
  27. NonStop
  28. Zephyr
  29. Azure Sphere OS
  30. Deos
  31. PikeOS
  32. Apache Mynewt
  33. AIX
  34. HP/UX
  35. Nintendo Wii and Gamecube with DevKitPro
  36. And many more that wolfSSL could work on…

wolfSSL has been developed from the ground up to work well in embedded devices and edge devices. This design has lent itself well for easily porting over to many different operating systems. If you are working on a project that has a need for some excellent security contact us at, or call us at +1 425 245 8247.

Download wolfSSL

wolfSSL Micrium Port Updated

Users of Micrium secured by wolfSSL rejoice! We recently added support for Micrium to utilize the hardware RNG of STM32 platforms. Also we updated the port to include the application configuration to take advantage of TCP IP settings in the Micrium network headers.

Micrium users can take advantage of wolfSSL’s best-tested security library, including support for TLS 1.3. and DTLS 1.3. For instructions on how to build and integrate the examples on your projects or to see the benchmark results, please see the README located in “IDE/ECLIPSE/MICRIUM”. For any questions or help getting wolfSSL up and running in your environment, please contact us at

As always, if you have questions on any of the above, please contact us at, or call us at +1 425 245 8247.

Download wolfSSL

Live Webinar: Linux Kernel Mode

Exciting news for Linux Kernel Module developers and developers who are interested in diving into Linux Kernel Module. Join us for a webinar on Linux Kernel Mode hosted by wolfSSL Engineer Daniel Pouzzner.

Save the date: 8/17/2023 at 10 am PT

After wolfSSL 4.6.0 introduced initial support for building as a Linux kernel module, and providing native wolfCrypt and wolfSSL APIs to other kernel modules in December 2020, 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.

wolfSSL engineer, Daniel Pouzzner, will showcase how wolfSSL Linux Kernel Mode can enhance your projects. It is your opportunity to learn knowledge and technical skills. Register now!

As always we will have a Q&A Session following the webinar.

If you have questions on any of the above, please contact us at, or call us at +1 425 245 8247.

Download wolfSSL

wolfSSL Supports TSIP v1.17

wolfSSL 5.6.3 adds support for Renesas TSIP v1.17 and extends some of the TLS handshake operations to use this cryptographic accelerator. TSIP v1.17 adds the ability to handle CertificateVerify messages over TLS. This feature is used for both validation and generation of messages exchanged with the server. Of course, both TLS1.2 and 1.3 can handle both ECC and RSA certificates.

Example applications for Renesas RX series MCUs with Renesas IDE e2studio project files are provided in the wolfSSL package, included in the /IDE/Renesas/e2studio/RXxx folders. Detailed instruction manuals written both in English and Japanese will help you get started with wolfSSL on these platforms quickly.

If you have any questions or want to know more details, lease contact us at, or call us at +1 425 245 8247.

Download wolfSSL

Posts navigation

1 2 3 4 5 6 173 174 175

Weekly updates