RECENT BLOG NEWS
Announcing wolfTPM v1.3 with TLS support
We are excited to announce wolfTPM v1.3, which adds support for TLS client, Certificate Signing Request (CSR) generation, PKCS #7 signing and verification and benchmarks. In addition to the features listed this release fixes some minor issues and adds in more wrappers for simplifying usage.
You can download the latest release from our website here:
https://www.wolfssl.com/products/wolftpm/
wolfTPM v1.3 (07/20/2018) Release Notes:
- Fixed the TIS TPM_BASE_ADDRESS to conform to specification.
- Fixed static analysis warnings.
- Fixed minor build warnings with different compilers.
- Fixed TPM failure for RSA exponents less than 7 by using software based RSA.
- Added TPM benchmarking support.
- Added functions to import/export public keys as wolf format.
- Added PKCS7 example to show sign/verify with TPM.
- Added CSR example to generate certificate request based on TPM key.
- Added CSR signing script ./certs/certreq.sh to create certificate using self-signed CA.
- Added TLS Client example that uses TPM based key for client certificate.
- Added support for wolfSSL WOLF_CRYPT_DEV callbacks to enable TPM based ECC and RSA private keys.
- Added ability to clear/reset TPM using ./examples/wrap/wrap_test 1
- Moved some of the example configuration into ./examples/tpm_io.h.
For questions please email us at facts@wolfssl.com.
wolfSSL Enables Gesytec to Easily Secure Communications Between Embedded Systems and the Cloud
Gesytec, a global leader in LON interfaces, provides worldwide software and hardware development solutions that focus on the improvement of industrial automation in industries such as restaurants, gas stations, hotels, grocery stores, and food distribution companies. One of Gesytec’s products, the GesySense Receiver \LAN is a device that consists of an embedded system that works to collect and record temperature statistics and relay them to a web-based user platform over a wireless network.
In order to avoid the compromise of data and to prevent potential attacks on the network, it became mandatory that the GesySense device data would need to be encrypted. As Gesytec was using Microchip’s PIC32MX boards, the cryptographic library they required needed to be very efficient in terms of resource usage. After thorough research, Gesytec landed at the conclusion that wolfSSL’s SSL/TLS library would be exactly what they wanted to secure the data from the GesySense device to the web-based platform.
To discover the reasons behind why wolfSSL was the optimal solution for Gesytec, please view the wolfSSL/Gesytec case study on our case studies page.
To learn more about Gesytec and their products, feel free to visit their website or contact them at info@gesytec.com.
For questions regarding the use of wolfSSL products in your embedded or IoT devices, please contact us at facts@wolfssl.com.
TLS 1.3 is now available in wolfSSL's embedded SSL/TLS library! Learn more here and don't forget to check out our product page.
wolfTPM Now Tested Nightly with Infineon OPTIGA (TM) Trusted Platform Module 2.0 SLB 9670
wolfTPM is a portable TPM 2.0 project designed for embedded use.
We have expanded our automated tests to ensure hardware support and functionality for wolfTPM in our commitment to having the best tested cryptography product lineup. Our Jenkins CI setup now tests the following build configuration every night!
Testing Hardware Setup
- Raspberry Pi 2 Model B Rev 1.2 (ARMv7 Processor rev 4 (v7l))
- Infineon OPTIGA (TM) Trusted Platform Module 2.0 SLB 967 (IRIDIUM9670 TPM2.0 LINUX).
wolfTPM Features
- This implementation provides all TPM 2.0 API’s in compliance with the specification.
- This uses the TPM Interface Specification (TIS) to communicate over SPI.
- The design allows for easy portability to different platforms:
- Native C code designed for embedded use.
- Single IO callback for hardware SPI interface.
- No external dependencies.
- Compact code size and minimal memory use.
- Examples for the Raspberry Pi and STM32 with CubeMX.
- Includes example code for most TPM2 native API’s.
- Includes wrappers for Key Generation, RSA encrypt/decrypt, ECC sign/verify and ECDH.
- Testing done using the Infineon OPTIGA SLB9670 module and LetsTrust TPM for Raspberry Pi.
Check out how to quickly build wolfSSL and wolfTPM on GitHub.
https://github.com/wolfSSL/wolfTPM
For examples on using the wolfTPM library check out the wrapper and native tests.
https://github.com/wolfSSL/wolfTPM/blob/master/examples/wrap/wrap_test.c
https://github.com/wolfSSL/wolfTPM/blob/master/examples/native/native_test.c
Please send any feedback or questions to us at facts@wolfssl.com
wolfCrypt JCE Provider Now Tested with Google Project Wycheproof
wolfCrypt JNI provides a Java, JNI-based wrapper to the native wolfCrypt API and implements wolfJCE as a JCE provider for Java’s built in security packages. wolfSSL is committed to providing the best tested cryptography available, and as such have expanded our automated testing of wolfCrypt JNI and JCE. Both FIPS 140-2 and non-FIPS builds of wolfCrypt JNI and wolfJCE are tested nightly through our Jenkins CI, with JUnit and Project Wycheproof unit tests.
Project Wycheproof is a test suite developed and maintained by the Google Security Team. Their unit tests use Java security packages (java.security and javax.crypto) to allow for multiple JCA/JCE provider implementations to be tested, including wolfJCE. Over 80 of their unit tests attempt to detect unexpected behavior, vulnerabilities to attacks, and other known weaknesses.
wolfSSL has confidence in having high quality security software built on a foundation of continuously expanding unit tests.
Please send any feedback or questions to us at facts@wolfssl.com.
wolfCrypt-JNI
Download: https://wolfssl.com/download
GitHub: https://github.com/wolfSSL/wolfcrypt-jni
Manual: https://www.wolfssl.com/docs/wolfcrypt-jni-jce-manual
Project Wycheproof
GitHub: https://github.com/google/wycheproof
And a shout out to Project Wycheproof maintainers:
- Daniel Bleichenbacher
- Thai Duong
- Emilia Kasper
- Quan Nguyen
wolfSSL and NGINX
Hi! We have been asked a number of times about wolfSSL integration with the nginx web server. If you are not familiar with Nginx, it is a high performance, high concurrency web server that is becoming extremely popular these days. You can learn more about nginx at nginx.com.
nginx and wolfSSL make a likely pairing because they are both lean, compact, fast, and scale well under high volumes of connections. The big news today is that wolfSSL + nginx is available in a public GitHub repository! We have added a new configure option “–enable-nginx” which will compile the wolfSSL libraries with nginx support.
For more info please contact us today facts@wolfssl.com!
wolfSSL repository for FreeRTOS classic and Amazon FreeRTOS
We have created a new repository for hosting the FreeRTOS classic and Amazon FreeRTOS support for wolfSSL located here:
https://github.com/wolfSSL/wolfssl-freertos
There are two pull requests with support for wolfSSL including demos:
FreeRTOS Classic v10.0.1 with wolfSSL/wolfMQTT demos:
https://github.com/wolfSSL/wolfssl-freertos/pull/1
- Added a wolfMQTT FreeRTOS TCP demo. This demo connects to the iot.eclipse.org MQTT broker with TLS on port 8883. It sends a counter publish message every second.
- Updated wolfSSL demo:
- Project built and tested against latest v3.14.4 release.
- Switched to using user_settings.h (WOLFSSL_USER_SETTINGS).
- Updated the certs (expired Jan 31, 2018).
- Stop tracking the .filter project file.
- Add submodule for wolfMQTT v1.0 plus FreeRTOS TCP support.
- Replace wolfSSL sources with submodule wolfSSL v3.14.4 plus some Win VS fixes.
- Initial FreeRTOS v10.0.1
Amazon FreeRTOS v1.2.3 port to use wolfSSL:
https://github.com/wolfSSL/wolfssl-freertos/pull/2
- Port of the Amazon FreeRTOS v1.2.3 to use wolfSSL.
- Added a new solution and project for demo at FreeRTOS-AWS/demos/pc/windows/visual_studio/aws_demo_wolf.sln.
- Added wolfssl as submodule.
Using wolfSSL and wolfCrypt from Java
Are you a Java developer looking for a industry-leading SSL/TLS and crypto implementation? If so, you’re in luck! wolfSSL provides has several options for you to use the native wolfSSL embedded SSL/TLS library and wolfCrypt cryptography libraries from Java.
wolfSSL TLS from Java
wolfSSL packages and maintains a JNI wrapper around the native C wolfSSL SSL/TLS library. This wrapper encapsulates the SSL/TLS functionality of wolfSSL to be used from Java applications.
This wrapper is a thin wrapper around the native wolfSSL C API. wolfSSL does not currently have a pluggable TLS-level JSSE provider. If this is something you are interested in, please contact us at facts@wolfssl.com! wolfSSL does offer a wolfCrypt-level pluggable JCE provider (see section below).
Full documentation on the wolfSSL JNI wrapper can be found here: wolfSSL JNI Manual
wolfSSL JNI ships with both a client and server example to make plugging it into a Java application easy!
wolfCrypt Cryptography from Java
wolfSSL packages and maintains a JNI wrapper and JCE provider for the native C wolfCrypt library. The “wolfcrypt-jni” package contains both a thin wolfCrypt JNI wrapper around the native C library as well as a pluggable wolfCrypt JCE provider.
Both of the following wrappers can be used with either normal wolfCrypt or wolfCrypt FIPS for those users who require a FIPS 140-2 validated cryptography library.
wolfCrypt JNI Wrapper
This wrapper is a thin wrapper around the native C wolfCrypt API. It is designed for users who want to use wolfCrypt directly from a Java application, but do not want to go through the default Java Security API.
wolfCrypt JCE Provider
The JCE (Java Cryptographic Extension) framework supports the installation of custom Cryptographic Service Providers which can implement a subset of the cryptographic functionality used by the Java Security API.
The wolfCrypt JCE provider has been tested with several different JDK variants, including OpenJDK, Oracle JDK, and Android. It also ships with pre-signed JAR files for use with Oracle JDK versions that will correctly verify JCE provider classes. OpenJDK does not have the requirement that JCE provider JAR’s be signed.
Classes and algorithms currently supported by the wolfCrypt JCE Provider:
Java Security Class | Supported Algorithms |
---|---|
java.security.MessageDigest | MD5, SHA-1, SHA-256, SHA-384, SHA-512 |
java.security.SecureRandom | HashDRBG |
javax.crypto.Cipher | AES/CBC/NoPadding DESede/CBC/NoPadding RSA/ECB/PKCS1Padding |
javax.crypto.Mac | HmacMD5, HmacSHA1, HmacSHA256, HmacSHA384, HmacSHA512 |
java.security.Signature | MD5withRSA, SHA1withRSA, SHA256withRSA, SHA384withRSA, SHA512withRSA SHA1withECDSA, SHA256withECDSA, SHA384withECDSA, SHA512withECDSA |
javax.crypto.KeyAgreement | DiffieHellman, DH, ECDH |
java.security.KeyPairGenerator | EC, DH |
You can download wolfSSL JNI as well as the wolfCrypt JNI wrapper and JCE provider from the wolfSSL download page. Please send any feedback or questions to us at facts@wolfssl.com.
TLS 1.3 combined with FIPS (#FIPS #TLS13)
For 2018, it's predicted that there will be more than 31 billion connectable IoT devices across the world. To put that number into perspective, imagine if every square mile on the Earth's surface was monitored by more than 150 IoT devices each. If this were square kilometers, there would be more than 60 IoT devices per square kilometer. With 31 billion devices potentially contributing to global internet traffic, this reveals a glaring need for an efficient and powerful way to secure data - and wolfSSL is the perfect solution.
wolfSSL is a lightweight TLS/SSL library that is targeted for embedded devices and systems. It has support for the most recent draft of the TLS 1.3 protocol, which is a secure protocol for transporting data between devices and across the internet. In addition, wolfSSL uses the wolfCrypt encryption library to handle its data encryption. Because there is a FIPS 140-2 validated version of wolfCrypt, this means that wolfSSL not only has support for the most current version of TLS, but it also has the encryption backbone to secure your data. FIPS 140-2 is a government certification that certifies that an encryption module has successfully passed rigorous testing and meets high encryption standards as specified by NIST.
Currently, wolfSSL is the only implementation of the TLS protocol that can support both the most recent version of TLS 1.3 and is FIPS 140-2 validated.
Some key benefits of combining TLS 1.3 with FIPS validated software include:
- Software becomes marketable to federal agencies - without FIPS, a federal agency is not able to use cryptographic-based software
- Single round trip
- 0-RTT (a mode that enable zero round trip time)
- After Server Hello, all handshake messages are encrypted.
And much more! For more information regarding the benefits of using TLS 1.3 or using the FIPS validated version of wolfCrypt, check out wolfSSL's TLS 1.3 Protocol Support and our wolfCrypt FIPS page.
For more details about wolfSSL, TLS 1.3, or if you have any other general inquiries please contact facts@wolfssl.com
To find out more about FIPS, check out the NIST FIPS publications or contact fips@wolfssl.com
wolfMQTT IBM Recipe
wolfMQTT is an MQTT client that has the capability to connect to the IBM Watson IoT cloud platform broker. This is useful as IBM's cloud platform allows users to potentially offload large amounts of data and/or computation to the cloud that is provided.
wolfMQTT comes ready with an example application titled "wiot" that shows users one way to communicate with the IBM Watson IoT broker. To use this example, all that needs to be done is to build the wolfMQTT library and then execute the wiot example.
An IBM Recipe that shows the process can be viewed here.
You can download the latest release from our website or clone on GitHub. For more information please email us at facts@wolfssl.com.
wolfSSL Intel SGX (#SGX) + FIPS 140-2 (#FIPS140)!
wolfSSL is pleased to announce the following addition to the wolfSSL FIPS certificate!
Debian 8.7.0 | Intel ® Xeon® E3 Family with SGX support | Intel®x64 Server System R1304SP |
Windows 10 Pro | Intel ® Core TM i5 with SGX support | Dell LatitudeTM 7480 |
The wolfCrypt FIPS validated cryptographic module has been validated while running inside an Intel SGX enclave and examples have been setup for both Linux and Windows environments.
Intel ® SGX (Software Guard Extensions) can be thought of as a black-box where no other application running on the same device can see inside regardless of privilege. From a security standpoint this means that even if a malicious actor were to gain complete control of a system including root privileges, that actor, no matter what they tried, would not be able to access data inside of this “black-box”.
An Intel enclave is a form of user-level Trusted Execution Environment (TEE) which can provide both storage and execution. Meaning one can store sensitive information inside and also move sensitive portions of a program or an entire application inside.
While testing, wolfSSL has placed both individual functions and entire applications inside the enclave. One of the wolfSSL examples shows a client inside the enclave with the only entry/exit points being “start_client”, “read”, and “write”. The client is pre-programmed with a peer to connect with and specific functionality. When “start_client” is invoked it connects to the peer using SSL/TLS and executes the pre-programmed tasks where the only data entering and leaving the enclave is the info being sent to and received from the peer. Other examples show placing a single cryptographic operation inside the enclave, passing in plain-text data and receiving back encrypted data masking execution of the cryptographic operations.
If you are working with SGX and need FIPS validated crypto running in an enclave contact us at fips@wolfssl.com or support@wolfssl.com with any questions. We would love the opportunity to field your questions and hear about your project!
Weekly updates
Archives
- January 2025 (7)
- December 2024 (22)
- November 2024 (29)
- October 2024 (18)
- September 2024 (21)
- August 2024 (24)
- July 2024 (27)
- June 2024 (22)
- May 2024 (28)
- April 2024 (29)
- March 2024 (21)
- February 2024 (18)
- January 2024 (21)
- December 2023 (20)
- November 2023 (20)
- October 2023 (23)
- September 2023 (17)
- August 2023 (25)
- July 2023 (39)
- June 2023 (13)
- May 2023 (11)
- April 2023 (6)
- March 2023 (23)
- February 2023 (7)
- January 2023 (7)
- December 2022 (15)
- November 2022 (11)
- October 2022 (8)
- September 2022 (7)
- August 2022 (12)
- July 2022 (7)
- June 2022 (14)
- May 2022 (10)
- April 2022 (11)
- March 2022 (12)
- February 2022 (22)
- January 2022 (12)
- December 2021 (13)
- November 2021 (27)
- October 2021 (11)
- September 2021 (14)
- August 2021 (10)
- July 2021 (16)
- June 2021 (13)
- May 2021 (9)
- April 2021 (13)
- March 2021 (24)
- February 2021 (22)
- January 2021 (18)
- December 2020 (19)
- November 2020 (11)
- October 2020 (3)
- September 2020 (20)
- August 2020 (11)
- July 2020 (7)
- June 2020 (14)
- May 2020 (13)
- April 2020 (14)
- March 2020 (4)
- February 2020 (21)
- January 2020 (18)
- December 2019 (7)
- November 2019 (16)
- October 2019 (14)
- September 2019 (18)
- August 2019 (16)
- July 2019 (8)
- June 2019 (9)
- May 2019 (28)
- April 2019 (27)
- March 2019 (15)
- February 2019 (10)
- January 2019 (16)
- December 2018 (24)
- November 2018 (9)
- October 2018 (15)
- September 2018 (15)
- August 2018 (5)
- July 2018 (15)
- June 2018 (29)
- May 2018 (12)
- April 2018 (6)
- March 2018 (18)
- February 2018 (6)
- January 2018 (11)
- December 2017 (5)
- November 2017 (12)
- October 2017 (5)
- September 2017 (7)
- August 2017 (6)
- July 2017 (11)
- June 2017 (7)
- May 2017 (9)
- April 2017 (5)
- March 2017 (6)
- January 2017 (8)
- December 2016 (2)
- November 2016 (1)
- October 2016 (15)
- September 2016 (6)
- August 2016 (5)
- July 2016 (4)
- June 2016 (9)
- May 2016 (4)
- April 2016 (4)
- March 2016 (4)
- February 2016 (9)
- January 2016 (6)
- December 2015 (4)
- November 2015 (6)
- October 2015 (5)
- September 2015 (5)
- August 2015 (8)
- July 2015 (7)
- June 2015 (9)
- May 2015 (1)
- April 2015 (4)
- March 2015 (12)
- January 2015 (4)
- December 2014 (6)
- November 2014 (3)
- October 2014 (1)
- September 2014 (11)
- August 2014 (5)
- July 2014 (9)
- June 2014 (10)
- May 2014 (5)
- April 2014 (9)
- February 2014 (3)
- January 2014 (5)
- December 2013 (7)
- November 2013 (4)
- October 2013 (7)
- September 2013 (3)
- August 2013 (9)
- July 2013 (7)
- June 2013 (4)
- May 2013 (7)
- April 2013 (4)
- March 2013 (2)
- February 2013 (3)
- January 2013 (8)
- December 2012 (12)
- November 2012 (5)
- October 2012 (7)
- September 2012 (3)
- August 2012 (6)
- July 2012 (4)
- June 2012 (3)
- May 2012 (4)
- April 2012 (6)
- March 2012 (2)
- February 2012 (5)
- January 2012 (7)
- December 2011 (5)
- November 2011 (7)
- October 2011 (5)
- September 2011 (6)
- August 2011 (5)
- July 2011 (2)
- June 2011 (7)
- May 2011 (11)
- April 2011 (4)
- March 2011 (12)
- February 2011 (7)
- January 2011 (11)
- December 2010 (17)
- November 2010 (12)
- October 2010 (11)
- September 2010 (9)
- August 2010 (20)
- July 2010 (12)
- June 2010 (7)
- May 2010 (1)
- January 2010 (2)
- November 2009 (2)
- October 2009 (1)
- September 2009 (1)
- May 2009 (1)
- February 2009 (1)
- January 2009 (1)
- December 2008 (1)