As you may know, wolfSSL has integrated our FIPS-certified crypto module, wolfCrypt, with OpenSSL as an OpenSSL engine, in a product we call wolfEngine. OpenSSL 3.0 has done away with the engines paradigm in favor of a new concept, called providers. wolfSSL now has a FIPS 140-2 solution for an OpenSSL 3.0 provider, allowing you to use the latest version of OpenSSL backed by our FIPS-certified wolfCrypt library.
wolfSSL is also in the process of getting certified for FIPS 140-3. Once certified, our OpenSSL 3.0 provider solution will also be FIPS 140-3 ready. Like wolfEngine, the wolfSSL provider for OpenSSL is an excellent pathway for users looking to get FIPS compliance fast while still using OpenSSL.
For more information, visit our blog post on the difference between FIPS 140-2 and FIPS 140-3.
If you have any questions regarding OpenSSL 3.0 provider solutions, please contact us at firstname.lastname@example.org.
We’re happy to announce that we’ve added experimental support to run wolfBoot as an EFI application! The Unified Extensible Firmware Interface (UEFI) is a specification that describes an interface between the operating system (OS) and the platform firmware and it replaces the old BIOS-like firmware. Now wolfBoot can run inside the UEFI environment on Intel x86_64 machines and load and verify other EFI applications.
This means that we can use it to boot and verify Linux (Linux supports booting as EFI application, a.k.a. EFI STUB) on UEFI machines.
UEFI has a several other interesting features that we plan to integrate in the future: such as SecureBoot and TPM.
To try wolfBoot EFI visit our repository on GitHub, you can also run an example on QEMU!
As usual for more information, please reach out to email@example.com!
The latest benchmarks of wolfSSL power consumption on an STM32L476G device are up (https://www.eembc.org/viewer/?benchmark_seq=13436). What we found is that using wolfSSL’s SP math (with assembly speed ups) is superior on the device. It has a positive impact on both the speed and power consumption.
With the measurements used with EEMBC (https://www.eembc.org/) higher final scores are better. Without using any optimizations in building wolfSSL the power usage collected was 2170 and performance was 502. Once turning on optimizations and SP assembly the power usage was 13200 and performance was 3050.
The energy score is derived from an inverted, weighted, micro Joules per iteration. Similarly the performance is an inverted, weighted, microseconds per iteration. ECDSA operations saw a significant performance and power usage improvement with SP math enabled and assembly optimizations compiled in. ECDSA operations are the biggest resource consumers with TLS handshakes and a good indication of how long and how much power a TLS connection will use.
For information about wolfSSL and power usage contact firstname.lastname@example.org.