RECENT BLOG NEWS

Join us for our final 2023 webinar, Security in Avionics – Tiger Lake and wolfBoot with DO-178C! Explore DO-178C Secure Boot with wolfBoot on Tiger Lake UP3 11th Gen Intel® Core™ Processors alongside wolfSSL Lead Embedded Software Engineer, Tesfa Mael, on December 21st at 10 am PT.

Save the date: December 21st, 10am PT

Ensure the safety, functionality, and security of avionics systems with a robust foundation in secure boot and firmware updates. Achieving certifications like DO-178C is crucial, necessitating comprehensive solutions. Join Tesfa as he navigates how to establish this foundation using Intel’s secure hardware solutions alongside wolfBoot, the secure bootloader developed by wolfSSL. wolfBoot, a portable and certifiable bootloader and firmware update solution, harnesses Intel technologies like AES-NI and AVX2 to optimize boot performance and bolster security.

Don’t miss this opportunity to gain insights into maximizing avionics security through DO-178C Secure Boot with wolfBoot on Tiger Lake UP3 11th Gen Intel® Core™ Processors. Elevate your technical skills and secure your avionics systems effectively with wolfSSL.

Register Today while seats are available.

If you have questions about any of the above, please contact us at facts@wolfSSl.com or call us at +1 425 245 8247.

Download wolfSSL Now

wolfTPM is a portable TPM 2.0 stack with backward API compatibility designed for embedded use, and the newly released wolfTPM v3.0.0 provides examples for Secure Boot solutions to store a Root of Trust in non-volatile (NV) memory.

Secure Boot for your microcontroller is essential to protect against malware during the earliest stages of your system boot, and establishing a Root of Trust is the first step towards that direction. The example was implemented with our Secure Boot solution wolfBoot.

See the documentation examples/boot/README.md and docs/TPM.md for more details on how to set up a Root of Trust with authentication and tamper protection using wolfTPM.

The design in the example for storage of public key based Root of Trust into TPM entails using AES-CFB parameter encryption for all communication (salted and bound) and deriving a password based on unique device parameters used as “auth” to load NV (authenticate). The approach is to anchor the public key into the TPM NV storage such that it cannot be erased or tampered with. The NV stores a hash of the public key and wolfBoot keeps the public key internally and programs the TPM with the NV if not populated. The platform NV is locked and created under the platform hierarchy. It is recommended to supply a derived “authentication” value to prevent TPM tampering. This authentication value is encrypted on the bus.

If you have questions about any of the above, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247.

Download wolfSSL Now

wolfTPM is a portable TPM 2.0 stack with backward API compatibility designed for embedded use, and the newly released wolfTPM v3.0.0 includes support for sealing/unsealing secrets to authority signed Platform Configuration Registers (PCR’s).

One of the most important features of the TPM 2.0 specification is the resolution of PCR brittleness. PCR brittleness is encountered when secrets like keys/data are sealed to PCR values and changes to hardware/software result in changes to the PCR values. With the altered PCR values, there is a mismatch of hashes and the secrets can no longer be unsealed. With the TPM 2.0 specification, it’s possible to seal/unseal secrets via cryptographic signatures of the PCR’s, removing the requirement to unseal then seal secrets whenever changes are made to the PCR values. wolfTPM now supports this feature.

See the documentation here examples/boot#secure-boot-encryption-key-storage for a wolfTPM example of using a private key to sign the state of a PCR, then seal and unseal a secret using the signed policy and a public key.

Our secure bootloader, wolfBoot, also supports this feature. See here docs/TPM.md#sealing-and-unsealing-a-secret.

If you have questions about any of the above, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247.

Download wolfSSL Now

Join our insightful webinar: wolfEngine vs wolfProvider, led by wolfSSL Senior Software Developer Anthony, on December 14th at 10 am PT.

Save the date: December 14th at 10 am PT

As you may be aware, the OpenSSL series 3.x has been launched, introducing a new FIPS 140-3 requirement. wolfSSL is here to simplify potentially challenging decisions for you. Anthony will explore the differences between wolfEngine and wolfProvider and demonstrate how to integrate them seamlessly with OpenSSL.

Sneak peek of the webinar:

• • Optimal Alternative: OpenSSL Compat layer
  • Understanding the OpenSSL 1.0.2, 1.1.1, and 3.x.y Branch Releases
  • Determining Suitable Branches for Engines and Providers
  • Utilizing wolfEngine and wolfProvider with the openssl app
  • Integrating wolfEngine and wolfProvider with the OpenSSL API
  • Available algorithms and cryptographic primitives
  • Insights on FIPS compliance

…And much more

This is an excellent chance to discover how you can efficiently meet the new OpenSSL requirements with wolfSSL. Anthony will showcase how wolfEngine and wolfProvider act as connectors between the OpenSSL and wolfCrypt FIPS, saving you time and effort.

Make sure to Register Today while seats are still available.

As always, our webinars will include Q&A sessions throughout. If you have questions about any of the above, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247.

Download wolfSSL Now

With our recent 5.6.4 release of wolfSSL/wolfCrypt, AES-XTS gains a newly optimized implementation for modern x86-64 CPUs. AES-XTS, standardized in IEEE P1619-2007 and NIST SP800-38E, and typically used for encrypting storage.

By leveraging AES-NI and AVX vectorized instructions, sustained throughput now exceeds 1.5 bytes per cycle for 256 bit keys, and 1.12 bytes per cycle for 512 bit keys, in both encrypt and decrypt modes.

The new wolfCrypt optimizations are fully kernel-compatible, enabling in-kernel disk encryption at state-of-the-art speeds and can exceed 5 GiB/s. Performance compares favorably with the Linux kernel’s optimized implementation, which attains 0.87 and 0.72 bytes per cycle with 256 and 512 bit keys respectively.

If you have questions about any of the above, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247

Download wolfSSL Now