U-Boot with wolfTPM

We are integrating wolfTPM into U-Boot. This will extend the TPM 2.0 capabilities in U-Boot to include signature verification and measured boot.

For many platforms we can replace U-Boot such as on the Xilinx UltraScale+ MPSoC.

Our wolfBoot allows many features including:
* Partition signature verification using ED25519, RSA and ECC
* Encryption of partitions
* Updating of partitions in the boot loader
* Measured boot with TPM 2.0 PCR registers
* Offloading to crypto coprocessors like the TPM 2.0 modules
* Version checking for updates
* Rollback on failed updates

For information on our wolfBoot TPM integration see https://www.wolfssl.com/products/wolfboot/.

If you are interested in our U-Boot wolfTPM integration please email facts@wolfssl.com.


Connect with wolfSSL:

wolfSentry Operating Environments

Our first preview release of wolfSentry, the IDPS (Intrusion Detection and Prevention System) for embedded and IoT systems, has platform support for Raspberry Pi, STM32 with CubeMX, Atmel ASF and Barebox. As well as native support for Microsoft Windows and Linux.

Here at wolfSSL we are always striving to be better so we would love to hear which operating environments and platforms you would like to see supported by wolfSentry. Contact us at facts@wolfssl.com!

wolfCrypt FIPS Operating Environments

wolfSSL fans! Do you like FIPS? Do you like virtual machines? Guess what. wolfSSL`s crypto library, wolfCrypt, is validated for FIPS 140-2 and in the process of being one of the first cryptography libraries to be validated for FIPS 140-3

As wolfCrypt is commonly used in standard operating environments because of its royalty-free pricing and excellent cross platform support, wolfCrypt FIPS has been validated on a number of Operating Environments (OEs). The current validated OE list for both wolfCrypt FIPS certificates (#2425 and #3389) are listed here for reference.  

Certificate #2425 Current OE List:

Operating SystemProcessorPlatform
Linux 3.13 (Ubuntu)Intel® Core™ i7-3720QM CPU @2.60GHz x 8HP EliteBook
iOS 8.1Apple™ A8iPhone™ 6
Android 4.4Qualcomm Krait 400Samsung Galaxy S5
FreeRTOS 7.6ST Micro STM32FuTrust TS Reader
Windows 7 (64-bit)Intel® Core™ i5Sony Vaio Pro
Linux 3.0 (SLES 11 SP4, 64-bit)Intel® Xeon® E3-1225Imprivata OneSign
Linux 3.0 (SLES 11 SP4, 64-bit) on Microsoft Hyper-V 2012R2 CoreIntel® Xeon® E5-2640Dell® PowerEdge™ r630
Linux 3.0 (SLES 11 SP4, 64-bit) on VMWare ESXi 5.5.0Intel® Xeon® E5-2640Dell® PowerEdge™ r630
Windows 7 (64-bit) on VMWare ESXi 5.5.0Intel® Xeon® E5-2640Dell® PowerEdge™ r630
Android Dalvik 4.2.2NXP i.MX6 MXT‐700‐NC 7” touch
Linux 4.1.15NXP i.MX5NX‐1200 NetLinx NX
Integrated Controller
Debian 8.8Intel Xeon® 1275v3CA PAM 304L Server
Windows Server 2012R2Intel® Xeon® E5335CA Technologies
Windows 7 Professional SP1Intel® Core™ i7‐2640MDell™ Latitude™ E6520
Debian 8.7.0Intel ® Xeon® E3 Family with SGX supportIntel® x64 Server System
Windows 10 ProIntel ® Core ™ i5 with SGX supportDell™ Latitude™ 7480
NET+OS v7.6 Digi International NS9210Sigma IV infusion pump
Linux 4.4 (SLES 12 SP3, 64‐
bit) on Microsoft Hyper‐V
2016 Core
Intel® Xeon® E5‐2650Dell® PowerEdge™ r720
Linux 4.4 (SLES 12 SP3, 64‐
bit) on VMWare ESXi 6.5.0
Intel® Xeon® E5‐2403Dell® PowerEdge™ r420

Certificate #3389 Current OE List:

Operating SystemProcessorPlatform
Linux 4.4
(Ubuntu 16.04 LTS)
Intel® Core™ i5-5300U CPU @2.30GHz x 4 with
Intel Ultrabook 2 in 1
Linux 4.4
(Ubuntu 16.04 LTS)
Intel® Core™ i5-5300U CPU @2.30GHz x 4
without AES-NI
Intel Ultrabook 2 in 1
Windows 10 (64-bit)Intel® Core™ i5-5300U CPU @2.30GHz x 4
with AES-NI
Intel Ultrabook 2 in 1
Windows 10 (64-bit)Intel® Core™ i5-5300U CPU @2.30GHz x 4
without AES-NI
Intel Ultrabook 2 in 1
OpenRTOS v10.1.1STMicroelectronics STM32L4xSTMicroelectronics
(Discovery Kit)
HP Imaging &
Printing Linux 4.9
ARM Cortex-A72 with PAAHP PN 3PZ95-60002
HP Imaging &
Printing Linux 4.9
ARM Cortex-A72 without PAAHP PN 3PZ95-60002
Windows 10
Intel® Core™ i7-7820 @2.9GHz x 4 with AES-NIRadar FCL Package
Windows 10
Intel® Core™ i7-7820 @2.9GHz x 4 without AES-NIRadar FCL Package
Linux socfpga
Cyclone V
Armv7 rev 0, Cortex A-9SEL 2700 Series 24-
Port Ethernet Switch
Red Hat Enterprise
Linux Workstation
Intel (R) Xeon(R) W-2155 @3.3GHz x 20 with PAADELL Precision 5820
Red Hat Enterprise
Linux Workstation
Intel (R) Xeon(R) W-2155 @3.3GHz x 20 without
DELL Precision 5820
Fusion Embedded
RTOS 5.0
Analog Devices ADSP-BF516 (BlackFin)Classone® IP Radio
Linux 4.12 Yocto
Freescale i.MX6 DualLite ARMv7 Cortex-A9 x2 with
Metasys® SNC Series
Network Control
Linux 4.12 Yocto
Freescale i.MX6 DualLite ARMv7 Cortex-A9 x2
without PAA
Metasys® SNC Series
Network Control
Nucleus 3.0 version 2013.08.1Freescale Vybrid VF500XL200 Radio
CodeOS v1.4CodeCorp CT8200 (ARM FA626TE)Series CR2700 Code Reader(s)
Linux 4.14ARMv8 Cortex A53 with PAASEL-2742S
Linux 4.14ARMv8 Cortex A53 without PAASEL-2742S
Windows CE 6.0ARM Cortex A8 ARMv7HP Color LaserJet Enterprise MFP M681
Linux 4.19ARMv8 Cortex A53 with PAACloudworx Video ENC-DEC
Linux 4.19ARMv8 Cortex A53 without PAACloudworx Video ENC-DEC
CMSIS-RTOS2 v2.1.3Silicon Labs EFM32G (Gecko)Alto

wolfSSL can easily add additional OEs to existing wolfCrypt FIPS certificates. To learn more about this process, please do not hesitate to send us an email at fips@wolfssl.com. We look forward to hearing from you.


strongSwan + wolfSSL + FIPS!

As some may be aware, wolfSSL added support for strongSwan in April of 2019. The upstream commit can be reviewed here: https://github.com/strongswan/strongswan/pull/133

Users can test the latest development master of wolfSSL with the latest version of strongSwan using the following setup:

wolfSSL Build and Installation Steps

$ git clone https://github.com/wolfSSL/wolfssl.git

$ cd wolfssl
$ ./autogen.sh

$ ./configure --enable-opensslall --enable-keygen --enable-rsapss --enable-des3 --enable-dtls --enable-certgen --enable-certreq --enable-certext --enable-sessioncerts --enable-crl --enable-ocsp CFLAGS="-DWOLFSSL_DES_ECB -DWOLFSSL_LOG_PRINTF -DWOLFSSL_PUBLIC_MP -DHAVE_EX_DATA"

$ make
$ make check
$ sudo make install

strongSwan Build and Installation Steps

# if the following packages are not already installed:
$ sudo apt-get install flex bison byacc libsoup2.4-dev gperf

$ git clone https://github.com/strongswan/strongswan.git
$ cd strongswan
$ ./autogen.sh

# if packages are missing autogen.sh must be re-run

$ ./configure --disable-defaults --enable-pki --enable-wolfssl --enable-pem
$ make
$ make check
$ sudo make install

wolfSSL has had interest in enabling FIPS 140-2/140-3 support with strongSwan so our engineers verified everything is working with the wolfCrypt FIPS 140-2 validated Module!

The steps wolfSSL used for testing are as follows:

Testing was done using the wolfSSL commercial FIPS release v4.7.0 which internally uses the wolfCrypt v4.0.0 FIPS 140-2 validated Crypto Module. It was located in the /home/user-name/Downloads directory on the target test system, Linux 4.15 Ubuntu 18.04 LTS running on Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz.

  1. wolfSSL was configured and installed with these settings:
./configure --enable-opensslall --enable-keygen --enable-rsapss --enable-des3 --enable-dtls --enable-certgen --enable-certreq --enable-certext --enable-sessioncerts --enable-crl --enable-ocsp CFLAGS="-DWOLFSSL_DES_ECB -DWOLFSSL_LOG_PRINTF -DWOLFSSL_PUBLIC_MP -DHAVE_EX_DATA -DFP_MAX_BITS=8192" --enable-ed25519 --enable-curve25519 --enable-fips=v2 --enable-intelasm --prefix=$(pwd)/../fips-install-dir
 make install
  1. A custom install location was used which equated to /home/user-name/Downloads/fips-install-dir and the configuration for strongSwan accounted for this.
  2. strongSwan was cloned to /home/user-name/Downloads with “git clone https://github.com/strongswan/strongswan.git
  3. StongSwan was configured and installed with these settings:
./configure --disable-defaults --enable-pki --enable-wolfssl --enable-pem --prefix=$(pwd)/../strongswan-install-dir wolfssl_CFLAGS="-I$(pwd)/../fips-install-dir/include" wolfssl_LIBS="-L$(pwd)/../fips-install-dir/lib -lwolfssl"
 make install
 make check
  1. In the make check stage of the test, it was observed that 1 test was failing.
 Passed 34 of 35 'libstrongswan' suites
 FAIL: libstrongswan_tests
 1 of 1 test failed
  1. Reviewing the logs it was apparent one of the RSA tests was failing.
  2. Upon further debugging it turned out the failure was a test in strongSwan that was attempting to create an RSA key size of 1536-bits.
Running case 'generate':
 DEBUG: key_sizes[_i] set to 1024
 DEBUG: key_sizes[_i] set to 1536
 DEBUG: key_sizes[_i] set to 2048
 DEBUG: key_sizes[_i] set to 3072
 DEBUG: key_sizes[_i] set to 4096

wolfSSL has a function RsaSizeCheck() which in FIPS mode will specifically reject any non FIPS RSA key sizes so this failure was not only expected, but it is a good thing for those wanting to use strongSwan in FIPS mode and ensure only FIPS-validated RSA key sizes will be supported!

wolfSSL is pleased that with the latest release of wolfSSL v4.7.0 and the wolfCrypt FIPS 140-2 module validated on FIPS certificate 3389, strongSwan support is working splendidly and wolfSSL engineers will be making efforts to ensure continued support into the future!

If you have any questions about wolfSSL, wolfCrypt FIPS, or strongSwan and wolfSSL together please contact our support staff anytime at support@wolfssl.com or via our Zendesk portal by registering and opening a support incident at wolfssl.zendesk.com.

wolfSSL devkitPro Support

devkitPro is a set of tool chains for compiling to gaming platforms. This includes the Nintendo Switch, 3DS, Wii, and Gamecube. If you need cryptographic or SSL/TLS capabilities in your games then wolfSSL has support for compiling with devkitPro. wolfSSL is a very lightweight and fast SSL/TLS library that will fit perfectly in a constrained game console environment.

This blog will showcase how to compile the wolfSSL testwolfcrypt program for Wii and run it in the Dolphin Emulator. It assumes that the devkitPro was installed in /opt/.

Compile wolfSSL using the devkitPPC tool chain:

./configure CFLAGS='-DDOLPHIN_EMULATOR -DDEVKITPRO -DGEKKO -DNO_WRITEV -I/opt/devkitpro/libogc/include -mrvl -mcpu=750 -mno-eabi -MMD -MP' LDFLAGS='-L/opt/devkitpro/libogc/lib/wii -lwiiuse -lbte -logc -lm' CC=/opt/devkitpro/devkitPPC/bin/powerpc-eabi-gcc RANLIB=/opt/devkitpro/devkitPPC/bin/powerpc-eabi-ranlib --host=ppc --enable-cryptonly --disable-shared --enable-static --disable-filesystem

Then convert the binary to a .dol file:

/opt/devkitpro/tools/bin/elf2dol wolfcrypt/test/testwolfcrypt ../testwolfcrypt.dol

The above command places the resulting binary in the directory that contains the wolfssl directory. Navigate to this directory in the Dolphin Emulator and run it:

All tests should pass and you may close the window. If you have additional questions about support for devkitPro targets, please write to us at facts@wolfssl.com.

wolfSSL Asynchronous Release v4.7.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: https://www.wolfssl.com/docs/intel-quickassist/

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

To find out more or get an evaluation please email facts@wolfssl.com.

BSD Kernel Mode compatibility for wolfSSL

We are in the process of adding BSD Kernel compatibility to wolfSSL. This means that our embedded SSL library would run in Kernel mode and use BSD based OE’s. The advantage of this project may include performance enhancement for device driver implementers that want SSL security. Stay tuned for more updates regarding this project. We would love to know do Kernel developers want an SSL library? Please comment!

cURL Release – cURL 7.77.0 – 200 OK

This post has been cross posted from Daniel Stenberg’s blog – originally posted here.

Welcome to the 200th curl release. We call it 200 OK. It coincides with us counting more than 900 commit authors and surpassing 2,400 credited contributors in the project. This is also the first release ever in which we thank more than 80 persons in the RELEASE-NOTES for having helped out making it and we’ve set two new record in the bug-bounty program: the largest single payout ever for a single bug (2,000 USD) and the largest total payout during a single release cycle: 3,800 USD.

This release cycle was 42 days only, two weeks shorter than normal due to the previous 7.76.1 patch release.


  • the 200th release
  • 5 changes
  • 42 days (total: 8,468)
  • 133 bug-fixes (total: 6,966)
  • 192 commits (total: 27,202)
  • 0 new public libcurl function (total: 85)
  • 2 new curl_easy_setopt() option (total: 290)
  • 2 new curl command line option (total: 242)
  • 82 contributors, 44 new (total: 2,410)
  • 47 authors, 23 new (total: 901)
  • 3 security fixes (total: 103)
  • 3,800 USD paid in Bug Bounties (total: 9,000 USD)


We set two new records in the curl bug-bounty program this time as mentioned above. These are the issues that made them happen.

This is a Use-After-Free in the OpenSSL backend code that in the absolutely worst case can lead to an RCE, a Remote Code Execution. The flaw is reasonably recently added and it’s very hard to exploit but you should upgrade or patch immediately.

The issue occurs when TLS session related info is sent from the TLS server when the transfer that previously used it is already done and gone.

The reporter was awarded 2,000 USD for this finding.

When libcurl accepts custom TELNET options to send to the server, it the input parser was flawed which could be exploited to have libcurl instead send contents from the stack.

The reporter was awarded 1,000 USD for this finding.

In the Schannel backend code, the selected cipher for a transfer done with was stored in a static variable. This caused one transfer’s choice to weaken the choice for a single set transfer could unknowingly affect other connections to a lower security grade than intended.

The reporter was awarded 800 USD for this finding.


In this release we introduce 5 new changes that might be interesting to take a look at!

  • Make TLS flavor explicit

As explained separately, the curl configure script no longer defaults to selecting a particular TLS library. When you build curl with configure now, you need to select which library to use. No special treatment for any of them!

  • No more SSL

curl now has no more traces of support for SSLv2 or SSLv3. Those ancient and insecure SSL versions were already disabled by default by TLS libraries everywhere, but now it’s also impossible to activate them even in special build. Stripped out from both the curl tool and the library (thus counted as two changes).

  • HSTS in the build

We brought HSTS support a while ago, but now we finally remove the experimental label and ship it enabled in the build by default for everyone to use it more easily.

  • In-memory cert API

We introduce API options for libcurl that allow users to specify certificates in-memory instead of using files in the file system. See CURLOPT_CAINFO_BLOB.

Favorite bug-fixes

Again we manage to perform a large amount of fixes in this release, so I’m highlighting a few of the ones I find most interesting!

  • Version output

The first line of curl -V output got updated: libcurl now includes OpenLDAP and its version of that was used in the build, and then the curl tool can add libmetalink and its version of that was used in the build!

  • curl_mprintf: add description

We’ve provided the *printf() clone functions in the API since forever, but we’ve tried to discourage users from using them. Still, now we have a first shot at a man page that clearly describes how they work.

This is important as they’re not quite POSIX compliant and users who against our advice decide to rely on them need to be able to know how they work!

  • CURLOPT_IPRESOLVE: preventing wrong IP version from being used

This option was made a little stricter than before. Previously, it would be lax about existing connections and prefer reuse instead of resolving again, but starting now this option makes sure to only use a connection with the request IP version.

This allows applications to explicitly create two separate connections to the same host using different IP versions when desired, which previously libcurl wouldn’t easily let you do.

  • Ignore SIGPIPE in curl_easy_send

libcurl makes its best at ignoring SIGPIPE everywhere and here we identified a spot where we had missed it… We also made sure to enable the ignoring logic when built to use wolfSSL.

  • Several HTTP/2-fixes

There are no less than 6 separate fixes mentioned in the HTTP/2 module in this release. Some potential memory leaks but also some more behavior improving things. Possibly the most important one was the move of the transfer-related error code from the connection struct to the transfers struct since it was vulnerable to a race condition that could make it wrong. Another related fix is that libcurl no longer forcibly disconnects a connection over which a transfer gets HTTP_1_1_REQUIRED returned.

  • Partial CONNECT requests

When the CONNECT HTTP request sent to a proxy wasn’t all sent in a single send() call, curl would fail. It is baffling that this bug hasn’t been found or reported earlier but was detected this time when the reporter issued a CONNECT request that was larger than 16 kilobytes…

  • TLS: add USE_HTTP2 define

There was several remaining bad assumptions that HTTP/2 support in curl relies purely on nghttp2. This is no longer true as HTTP/2 support can also be provide by hyper.

  • normalize numerical IPv4 hosts

The URL parser now knows about the special IPv4 numerical formats and parses and normalizes URLs with numerical IPv4 addresses.

  • Timeout, timed out libssh2 disconnects too

When libcurl (built with libssh2 support) stopped an SFTP transfer because a timeout was triggered, the following SFTP disconnect procedure was subsequently also stopped because of the same timeout and therefore wasn’t allowed to properly clean up everything, leading to a memory-leak!

IRC network switch

We moved the #curl IRC channel to the new network libera.chat. Come join us there!

Next release

On Jul 21, 2021 we plan to ship the next release. The version number for that is not yet decided but we have changes in the pipeline, making a minor version number bump very likely.


  • wolfSSL offers Curl support is available, and part of that support revenue goes into finding and fixing these kinds of vulnerabilities.  
  •  Customers under curl support can get advice on whether or not the advisories apply to them.
  •  24×7 support on curl is available, and can include pre-notification of upcoming vulnerability announcements.


Contact us at facts@wolfssl.com to learn more.

Command-line Utility: Here’s What We’re Adding Next

wolfSSL has a command-line utility, it’s called wolfCLU. As promised, here’s a sneak peek of notable additions to wolfCLU that are coming soon:

  1. PKEY and certificate public key output
  2. Certificate request creation
  3. Updates to human readable text output of certificates

What do you want to see from wolfCLU? Download on GitHub today and write to facts@wolfSSL.com with your input!

Download wolfCLU: https://github.com/wolfSSL/wolfssl-examples/tree/master/wolfCLU
Love it? Star us on GitHub!

Did You Know We Have a Command-line Utility?

In case you didn’t know, wolfSSL has a portable command line utility. You can download wolfCLU on Github today for use with the wolfSSL embedded SSL/TLS library! wolfCLU (Command Line Utility) is backed by the best-tested crypto using wolfCrypt and it can make use of FIPS builds with wolfSSL!

wolfCLU currently has the following features:
– Support for ED25519 sign and verify
– Autoconf for portability
– Encrypt a file and store it locally on your computer
– Decrypt that file after it has been encrypted, or send it via email to your friend, if he/she knows the password and algorithm used for encryption, they can then decrypt it on their computer
– Hash a single file (IE a zip archive) for verification
– Benchmark the currently configured Algorithms
– X509 parsing and print out

Download wolfCLU: https://github.com/wolfssl/wolfclu
Love it? Star us on GitHub! Contact facts@wolfssl.com with any questions or for help getting started with wolfCLU.

Posts navigation

1 2