Even FPGA softcore microprocessors need security. wolfSSL supports Xilinx MicroBlaze and Altera Nios II as well as Zynq SoCs with acceleration using XilSecure. For new and legacy projects, efficient security is available with first-class support.
See the Xilinx Vitis and Vivado README. For Nios II, from the Quartus developer environment run
wolfSSL provides leading TLS 1.3 capabilities in a small memory footprint, and also offers FIPS 140-2/140-3 and DO-178 certified versions.
Please contact us at firstname.lastname@example.org with any questions you have on wolfSSL, or just give us a call!
FIPS 140-2 requires the use of validated cryptography in the security systems implemented by federal agencies to protect sensitive information. The wolfCrypt Module is a comprehensive suite of FIPS Approved algorithms. All key sizes and modes have been implemented to allow flexibility and efficiency.
The National Institute of Standards and Technology (NIST) is sending FIPS cert #2425 into sunset June 2021. For customers who will be impacted, the wolfCrypt Cryptographic Module maintains its #3389 certificate and can be used in conjunction with the wolfSSL embedded SSL/TLS library for full TLS 1.3 client and server support. Upgrade your FIPS cert with wolfSSL to stay afloat and benefit from:
- Algorithm support for TLS 1.3!
- New algorithms such as AES (CBC, GCM, CTR, ECB), CVL, Hash DRBG, DSA, DHE, ECDSA (key generation, sign, verify), HMAC, RSA (key generation, sign, verify), SHA-3, SHA-2, SHA-1, and Triple-DES
- Hardware encryption support for NXP’s Cryptographic Assistance and Assurance Module (CAAM), NXP Memory-Mapped Cryptographic Acceleration Unit (mmCAU), Intel’s AES-NI, and more
- Support for secure elements and TPM’s
- Interoperability with wolfBoot, wolfSSH, and wolfTPM
- Integration support for third party libraries such as strongswan, nginx, python and more
Contact us to upgrade to FIPS cert #3389 at email@example.com.
Learn more about wolfSSL support for FIPS cert #3389: https://www.wolfssl.com/wolfcrypt-fips-certificate-3389-3/
For a list of supported Operating Environments for wolfCrypt FIPS, check our FIPS page: https://www.wolfssl.com/license/fips/
Our FIPS Story
wolfSSL is currently the leader in embedded FIPS certificates. We have a long history in FIPS starting with wolfCrypt FIPS 140-2 Level 1 Certificate #2425 as well as wolfCrypt v4 FIPS 140-2 Level 1 Certificate #3389. wolfSSL partners with FIPS experts KeyPair to bring you FIPS consulting services, and high assurance along each step of your FIPS certification process. Additionally, wolfSSL will be the first implementation of FIPS 140-3.
wolfSSL also provides support for a wolfCrypt FIPS Ready version of the library! wolfCrypt FIPS Ready is our FIPS enabled cryptography layer code included in the wolfSSL source tree that you can enable and build. You do not get a FIPS certificate, you are not FIPS approved, but you will be FIPS Ready. FIPS Ready means that you have included the FIPS code into your build and that you are operating according to the FIPS enforced best practices of default entry point, and power on self test.
wolfCrypt FIPS Ready can be downloaded from the wolfSSL download page located here: https://www.wolfssl.com/download/. More information on getting set up with wolfCrypt FIPS Ready can be found in our FIPS Ready User guide here: https://www.wolfssl.com/docs/fips-ready-user-guide/
Version 1.7.0 of wolfSSL JNI and JSSE is now available for download! wolfSSL JNI and JSSE provides Java applications with a convenient Java API to the widely-used wolfSSL embedded SSL/TLS library, including support for TLS 1.3! This package provides both a Java JSSE Provider as well as a thin JNI wrapper around native wolfSSL.
Release 1.7.0 has bug fixes and new features including:
- Fixes for Infer analysis warnings
- Throw exception in DEFAULT_Context creation if engineInit() fails
- Defer creating DEFAULT WolfSSLContext until first use
- Check if Socket is open before doing TLS shutdown in WolfSSLSocket.close()
- Only load X509TrustStore issuers when needed by native wolfSSL verification
- Fix compiler warnings when used with older versions of native wolfSSL
- Verify and load intermediate CA certs in WolfSSLTrustX509.certManagerVerify()
- Add support for setSoTimeout() in WolfSSLSocket
- Fix suites length check in WolfSSLEngineHelper.setLocalCiphers()
- Check for connection closed before completing handshake in SSLSocket.read/write
wolfSSL JNI and JSSE 1.7.0 can be downloaded from the wolfSSL download page and the wolfSSL JNI Manual can be found here.
For any questions, or to get help using wolfSSL in your product or project, contact us at firstname.lastname@example.org.
We would like to personally invite you to a webinar presented by wolfSSL.
In this webinar, we will talk about using hardware-based security with wolfTPM to protect your software and embedded systems. By using a TPM you can add secure storage for cryptographic keys and other secrets. More advance use is to protect the firmware and system settings of your IoT/Edge devices in the field.
When: Jan 20, 2021 08:00 AM Pacific Time (US and Canada)
Topic: Webinar: wolfTPM Roadmap and Best Differentiators
Register in advance for this webinar:
After registering, you will receive a confirmation email containing information about joining the webinar.
See you there!
Please contact us at email@example.com with any questions about the webinar. For technical support, please contact firstname.lastname@example.org or view our FAQ page.
In the meanwhile, check out the wolfSSL embedded SSL/TLS library, star us on Github, and learn more about the latest TLS 1.3 is available in wolfSSL.
The wolfSSL embedded SSL/TLS library includes three different math libraries which can be used to support wolfCrypt’s cryptographic operations – the Normal Math library, the fastmath library, and SP math. To help our users decide which math library is right for them, we have put together a helpful comparison matrix!
The wolfSSL Math Library Comparison Matrix, included below, shows the strengths and weaknesses of the 3 math options offered by wolfSSL. If you have any commentary or feedback please reach out to our team at email@example.com or firstname.lastname@example.org!
A major release for wolfTPM came out at the end of 2020 and is now available for download from our website. This release brings many new features:
- Native support for using TPM2.0 hardware with wolfTPM under Microsoft Windows
- TPM simulator support for even easier development with wolfTPM and MacOS users
- Protection from MITM (man-in-the-middle) attacks using TPM2.0 Parameter Encryption. wolfTPM supports both TPM2.0 options for MITM protection, XOR encryption and AES CFB.
- HMAC Session support for verification of peer authenticity and integrity.
This release also adds multiple new examples: TPM key generation and key loading examples with options to store the key to disk and use parameter encryption to protect from MITM. Added is support for importing external private keys and easy re-loading. And for those who use the internal TPM clock for reference, there is now a TPM clock increment example.
Among the other enhancements of our portable TPM2.0 library are the use of HMAC sessions and new wolfTPM wrappers for easier work with TPM sessions and authorization of TPM objects.
Please contact us at email@example.com for more information and help for taking advantage of the new wolfTPM features to better protect your systems.
Back in January of 2018 wolfSSL added support for use with the Open Whisper Systems Signal Protocol C Library! This means that you can now develop Signal applications using wolfCrypt as the underlying cryptography provider.
For those unfamiliar with the Signal Protocol, it is described on their GitHub page as “A ratcheting forward secrecy protocol that works in synchronous and asynchronous messaging environments.”
wolfSSL also has a JSSE provider that can be used with Android. This can seamlessly replace the default provider, giving all the benefits that come with using wolfSSL. Such as; extra performance boosts, access to our stellar support, and FIPS certifications to name a few items. Instructions on using the wolfSSL JSSE with Android can be found here https://www.wolfssl.com/docs/installing-a-jsse-provider-in-android-osp/.
wolfCrypt Signal Protocol Integration
By design, the Signal Protocol C Library does not depend on any SSL/TLS or cryptography library. Instead, Signal allows the application to register a crypto provider at runtime. We recently ported the wolfCrypt cryptography library into the “libsignal-protocol-c” test code and added a CMake configuration to build the libsignal-protocol-c test programs using cryptography from wolfSSL.
With this build option and wolfCrypt integration, Signal application developers can choose to use cryptography from wolfSSL instead of OpenSSL. Thanks to wolfSSL’s small footprint size, low memory usage, and broad platform support, application developers can more easily use the Signal Protocol C Library on small resource-constrained platforms and embedded systems.
For more information on using wolfCrypt with Signal, contact us at firstname.lastname@example.org!
The team here at wolfSSL is putting together a Sparkplug example that we’d like to share with you! The Sparkplug specification is useful for Industrial IoT system developers building on top of MQTT. Sparkplug defines a set of device states, adds topic naming structures, and defines payload formats. The wolfMQTT client library is perfectly suited to help secure your IIoT project since it is already integrated with wolfSSL!
For more information send a quick note to email@example.com
You can download the latest release here: https://www.wolfssl.com/download/
Or clone directly from our GitHub repository: https://github.com/wolfSSL/wolfMQTT
While you’re there, show us some love and give the wolfMQTT project a Star!
Last year wolfSSL fixed 8 vulnerabilities and documented them in the wolfSSL embedded SSL/TLS library release notes. Thanks to all of the researcher reports, and to the dedicated wolfSSL team, the fixes were identified and resolved rapidly. How rapidly you may ask? The average time to get a fix submitted for review on the vulnerabilities listed in 2020 was just over 26 hours.
Thanks to the researchers that submitted reports!
- Gerald Doussot from NCC group
- Lenny Wang of Tencent Security Xuanwu LAB
- Ida Bruhns from Universität zu Lübeck and Samira Briongos from NEC Laboratories Europe
- Alejandro Cabrera Aldaya, Cesar Pereida García and Billy Bob Brumley from the Network and Information Security Group (NISEC) at Tampere University
- Paul Fiterau of Uppsala University and Robert Merget of Ruhr-University Bochum
- Pietro Borrello at Sapienza University of Rome
If you have a vulnerability to report or would like more information, contact us at firstname.lastname@example.org, the wolfSSL development team takes vulnerabilities seriously.
wolfSSL is developing a library to handle the location of where crypto operations run amongst multiple cores. For large systems that have many sign/verify operations happening at once this library would be able to distribute those sign/verify requests based on a user’s input. In addition to managing where the operation runs it can be used to plug in hardware acceleration for handling requests that come in. An example use case would be having 3 cores for generic lower priority operations and saving 1 core that has hardware acceleration for fast, real time responses, that would run high priority operations.
Contact us at email@example.com with any questions, or for more details! The wolfSSL embedded SSL/TLS library also supports TLS 1.3, FIPS 140-2/3, and DO-178.