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 firstname.lastname@example.org with any questions.
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 email@example.com 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 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 firstname.lastname@example.org.
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 wolfssl-4.4.0-gplv3-fips-ready.zip 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 email@example.com anytime, we are always happy to help in any way we can!