RECENT BLOG NEWS
wolfBoot support for the STM32C0 in 2024
We have added wolfBoot support for the new STM32C0. This is a low cost MCU similar to the STM32G0 based on a Cortex-M0 (48MHz). It is a very low cost general purpose 32-bit MCU with up to 32KB flash and 12KB RAM.
Our wolfBoot secure bootloader is the only solution available for this platform thanks to our small code size. Most STM32 parts are supported with wolfBoot out of the box.
The default STM32C0 configuration uses RSA 2048-bit and SHA2-256 and is less than 10KB. This leaves 10KB for the application partition, 10KB for the update partition and one 2KB sector for swap.
STM32C0 documentation and build steps can be found here.
See our video series with ST for a tutorial on using wolfBoot.
wolfBoot Features:
- Written in C for bare-metal use
- Small footprint to run on small embedded devices
- Memory safety (no malloc/free)
- Support for on-board or external SPI flash
- Simple partitioning and header scheme
- Abstracted HAL design for CPU speed and flash
- Bootloader handles swapping and loading of partitions
- Key tools for key generation/import and signing
- Encrypted updates
- Delta updates (only differences)
Signature algorithms supported:
- ECC (SECP256R1,SECP384R1)
- RSA (2048/3072/4096)
- ED25519
- ED448
- Post Quantum LMS and XMSS
Firmware image integrity using hash digest:
- SHA2-256
- SHA2-384
- SHA3-384
Flexible partition scheme determined at build-time:
- Bootloader (10-30KB)
- Application
- Update
- Swap (1 sector)
- And custom partition ID’s
Reliable Firmware update mechanism:
- Independent from the update transport mechanism
- Fallback to a previous version when the update fails
- Resume interrupted swap operations during update, in case of power failure
Support for STM hardware crypto acceleration:
- STM32 HASH/AES/PKA
- ST33TP* TPM 2.0 using wolfTPM
- STSAFE
If interested in trying our wolfBoot on the STM32C0 or curious about post-quantum signature support in wolfBoot please contact facts@wolfSSL.com or call us at +1 425 245 8247.
Download wolfSSL Now
What is AUTOSAR and How is Crypto Used with it?
AUTOSAR stands for AUTomotive Open System ARchitecture and is a group of companies that set a standardized way for components used in the automotive industry to interface with each other. There are multiple release versions of the AUTOSAR documents and standardizations, but the ones we focus on are those that consume cryptography, and in particular how the AUTOSAR cryptography standards can consume wolfCrypt. The AUTOSAR crypto stack is made up of Crypto Service Manager, Crypto Interface, and Crypto Driver. Where the Crypto Service Manager is the highest level of abstraction and the Crypto Driver is at the lowest level, the driver being either provided by a cryptography implementation done in software or hardware or resident in an automotive HSM. wolfCrypt is callable in all of the above scenarios through the AUTOSAR abstraction API’s. One of the benefits of using AUTOSAR with wolfCrypt is seamless transition between our software encryption, our encryption calling into hardware encryption, or calling into an HSM as you re-use your higher level code in successive projects.
If you have a need for software cryptography operations that conform to the AUTOSAR specifications contact us at facts@wolfSSL.com. You can find some example code from here.
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
Live Webinar: Getting Started with wolfMQTT
Welcome to the third episode of the Getting Started series! Join us for “Getting Started with wolfMQTT” on February 15th at 10 am PT, presented by wolfSSL Senior Software Engineer, Eric. Explore how wolfMQTT, a client implementation of the MQTT protocol written in C for embedded systems, can bolster your IoT security. Eric will guide you from foundational concepts to advanced features, empowering you to effectively utilize the capabilities of wolfMQTT.
In this webinar, you’ll delve into key topics including:
- The significance of having a dedicated IoT protocol
- An overview of the MQTT protocol
- Specifications supported by the wolfMQTT client
- Understanding the architecture of wolfMQTT
- Configuration and build processes
- Real-world wolfMQTT examples
- Insights into future development plans
Watch the webinar now: Getting Started with wolfMQTT
Don’t miss this opportunity to enhance your understanding of MQTT and strengthen your security infrastructure with wolfMQTT. Watch now!
As always, our webinars will include Q&A sessions throughout the webinar. 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
wolfBoot Support for Renesas RZ/N2L
wolfBoot currently support both Renesas RA6M4 and RX72N MCUs. Supporting other Renesas MCUs for wolfBoot should not be difficult. We are considering the addition of Renesas RZ/N2L support for wolfBoot, which will build on our existing support at the wolfSSL and wolfCrypt level for Renesas RZ/N2L.
The Renesas RZ/N2L uses a high-performance Arm Cortex-R52 core to easily add network functionality onto industrial equipment and machines. The RZ/N2L is supported by an open and flexible ecosystem concept – the Flexible Software Package (FSP), built on FreeRTOS – and is expandable to use other RTOS and middleware solutions.
If you are interested in wolfBoot support on the RZ/N2L or 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
wolfSSH Adds Support for Zephyr RTOS
The wolfSSH 1.4.15 release includes brand new support for the Zephyr RTOS. wolfSSH is a lightweight SSH library designed for embedded systems. It is a performant and low footprint solution, making it an ideal choice for IoT devices. The Zephyr RTOS is an open-source, scalable, and flexible real-time operating system tailored for resource-constrained devices. Its modular architecture and broad hardware support make it a popular choice for various embedded applications.
wolfSSH is introduced as a new module in the Zephyr ecosystem. Necessary steps to get started include setting up wolfSSH as a Zephyr module, modifying the west manifest, and finally building your project. In-depth instructions to set up wolfSSH with Zephyr can be found at the wolfSSH Github.
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
Skipping the Cookie Exchange in DTLS 1.3
wolfSSL 5.6.6 introduces the option for DTLS 1.3 servers to skip the cookie exchange on a session resumption. The cookie exchange is a security mechanism employed during the resumption of a DTLS 1.3 session. When a client wants to resume a previous DTLS 1.3 session, it sends a session ticket to the server, which may respond by issuing a “cookie” to the client. This cookie serves as a challenge-response mechanism, requiring the client to present it during the resumption attempt. The purpose of this exchange is for the client to demonstrate reachability at their apparent network address. In some cases, you may choose to skip the cookie exchange if the client presents a valid ticket or pre-shared key (PSK).
To resume a DTLS 1.3 session without the cookie exchange:
- Compile wolfSSL with WOLFSSL_DTLS13_NO_HRR_ON_RESUME defined. Either:
- When compiling with configure add CPPFLAGS=-DWOLFSSL_DTLS13_NO_HRR_ON_RESUME
- When compiling with user settings add #define WOLFSSL_DTLS13_NO_HRR_ON_RESUME
- Call wolfSSL_dtls13_no_hrr_on_resume(ssl, 1) on the WOLFSSL object to disable the cookie exchange on resumption
- Continue like with a normal connection
If you have any questions about using DTLS 1.3 in wolfSSL, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247.
Download wolfSSL Now
Live Webinar: Solutions for the Satellite Industry
Get ready to learn the best practice for satellite cybersecurity with wolfSSL.
Join us for a webinar on “Solutions for the Satellite Industry” on February 8th at 10 am PT presented by wolfSSL Software Engineer, András. He will delve into robust solutions and best practices to safeguard satellite cybersecurity. This webinar is a must-attend for professionals in the aerospace and cybersecurity industries.
Watch the webinar here: Solutions for the Satellite Industry
Sneak Peek of the webinar:
- Introduction to wolfSSL
- Key wolfSSL Technologies for Satellite Security
- High-Quality SSL/TLS Testing
- Q&A
Don’t miss out on this opportunity to gain insights into the latest advancements in satellite cybersecurity. András will guide you through how FIPS, wolfBoot (Secure Boot), wolfTPM, wolfEntropy, and SSL/ TLS testing contribute to a secure satellite environment. Discover how wolfSSL conducts testing to ensure the highest level of security in SSL/TLS protocols. Watch now and get answers to your specific questions from András.
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
Overview of Testing in wolfSSL
The security of wolfSSL products is always on the wolfSSL team’s mind and holds high importance. Conducting regular, diligent, and well-planned testing helps maintain wolfSSL’s robustness and security. The wolfSSL team strives to write and maintain clean, readable, and understandable code.
- API Unit Testing: Unit tests are in place to test API functions for correct behavior. This helps maintain library consistency across releases and as the code evolves. It ensures delivery of a high quality, well tested API to end users with each software release. API unit tests are run with each “make check” of wolfSSL.
- Cipher Suite Testing: wolfSSL supports an extensive list of cipher suites, which are all tested with every “make check” using the wolfSSL example client and example server. Each cipher suite is tested not only in the default configuration, but also in non-blocking mode and with client authentication both turned on and off.
- Algorithm Testing: The security of the SSL/TLS implementation depends on the correctness and robustness of the underlying cryptography library, wolfCrypt. The wolfssl team tests all algorithms using NIST test vectors in addition to running a CAVP test harness used for FIPS 140-2 and 140-3 validations. Testing is done on both big and little endian platforms for portability.
- Benchmark Testing: The wolfSSL team engages in the ever expanding universe of benchmark testing, taking into consideration sizing, transmission rates, connection speeds, and cryptography performance. A version of the benchmark suite is included in every download for users to enjoy!
- Static Analysis: wolfSSL does static analysis on the entire codebase using not only one, but multiple different static analysis tools. Currently Coverity Scan, CodeSonar, clang scan-build, and Facebook infer. These tools help to automatically find bugs including those on low-traffic code paths.
- Detecting Memory Errors: Memory errors are mitigated by using valgrind on a regular and automated basis. This helps find memory errors including invalid access, use of undefined values, incorrect freeing of dynamic memory, and memory leaks.
- Interop Testing: Interoperability checks are done with other Open Source TLS implementations, including OpenSSL, BoringSSL, and GnuTLS. This helps to catch any protocol implementation errors in either wolfSSL or the implementation being tested against. Testing is also done outside of a closed environment by connecting to servers in the real world running unknown SSL/TLS implementations.
- Real World Builds: Builds with a series of ‘real’ applications, like cURL, wget, pppd, OpenSSH, stunnel, lighttpd, etc. For some wolfSSL customers with top level support, the wolfSSL team also tests building the latest library version against those customer applications.
- Compiler Testing: Some users compile wolfSSL with a variety of different compilers. As such, wolfSSL tests compilation with many different compilers and toolchains including but not limited to: gcc/g++, clang, icc, Visual Studio, CodeWarrior, KDS, LPCXpresso, MPLAB XC, TI CCS, Keil, IAR, Espressif IDF, Cygwin, MinGW, CrossWorks, Arduino, Wind River Workbench.
- Peer Review: More eyes on a codebase reduces bugs that end up in a final product. Internally, the wolfSSL team operates using a “Fork and Pull Request” model. This means that every commit that makes it into the wolfSSL master branch has been reviewed and tested by a minimum of two engineers.
- Code size increase monitoring: wolfSSL has tests that give alarms when a particular commit greatly increases the code size for a particular build. Active Monitoring of how much the code has grown since the last release ensures that it is within an acceptable range.
- Third Party Testing: wolfSSL code is regularly reviewed by university researchers, customer and user security teams, FIPS and certification labs, and other Open Source users. This helps put more eyes on the code and product architecture.
- Fuzz Testing: wolfSSL tests using several different software fuzzers, including an in-memory fuzzer, a network fuzzer, OSS-fuzz, libfuzzer, tlsfuzzer, and AFL. Fuzz testing bombards the program with invalid, unexpected, and random data that then allows for observing if there are potential memory leaks or logic errors. This allows us to catch bugs that could turn into potential vulnerabilities if released in a final release.
- Protocol Analysis: TLS-Attacker, a Java-based framework for analyzing TLS libraries, helps us analyze that wolfSSL correctly conforms to the SSL/TLS specification.
- Continuous Integration (CI): Leveraging Jenkins as well as GitHub Actions, allows wolfSSL to run tests on each commit submitted to the wolfSSL code repository. Tests run on each commit include testing of the FIPS build, numerous build options (customer/user/common), running valgrind, and doing static analysis with scan-build.
- Nightly Test Cycle: Each night extended tests are run that last longer than the typical ones during the work day. These extended tests are more in-depth than CI testing and puts results in wolfSSL engineers’ inboxes each morning. Some tests included in the nightly cycle include extended build option testing on multiple platforms with multiple compilers, and extended fuzz testing.
If you have specific questions about how the wolfSSL team tests, please contact us at facts@wolfssl.com or call us at +1 425 245 8247. If you would like the wolfSSL team to include your SSL/TLS or crypto implementation in interop testing, please let us know! Likewise, if you would like to include wolfSSL in your own test framework, the wolfSSL team would be happy to discuss.
Download wolfSSL Now
wolfSSL Adds Support for 0.5-RTT Data in (D)TLS 1.3
(D)TLS 1.3 support for 0.5-RTT (round trip time) data has been introduced to wolfSSL in the latest release (5.6.6). 0.5-RTT data is an optimization in (D)TLS 1.3 that significantly reduces latency and improves overall performance of application data. The full handshake requires two full round trips to start sending data while this functionality allows the server to send application data along with its final flight of handshake messages. This new addition works well with our support for early data (also known as 0-RTT data). An embedded device is able to resume a connection, send early data with its connection request, and receive a response immediately within one RTT.
Client Server ClientHello --------> ServerHello EncryptedExtensions CertificateRequest Certificate CertificateVerify Finished <-------- 0.5-RTT Application Data Certificate CertificateVerify Finished --------> Application Data <-------> Application Data
Diagram showing 0.5-RTT data in a full TLS 1.3 handshake
If you would like to learn more about (D)TLS 1.3 in wolfSSL, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247.
Download wolfSSL Now
Testing For Your Use Cases
Here at wolfSSL, we love to tout that we have the best tested cryptography library in the world and we stand by that statement 100%. You can even have a look at some of the unit tests in all our products. Simply build any one of our products and execute make check to see our testing in action.
But our testing does not end there. We have a massive continuous integration system that runs tests on:
- nightly basis
- weekly basis
- each time a commit is pushed to a pull request
You can get a hint of what goes on by looking at an active PR for any of our products (https://github.com/wolfSSL/). The content of those tests cannot be made public because some of them contain confidential customer usage patterns.
We test configurations submitted by our Premium support level customers (https://www.wolfssl.com/products/support-and-maintenance/). This allows them to rest assured that when we have a release, their configuration has been tested during development and will not have unpleasant surprises when they integrate it. Are you a Premium support level customer who hasn’t sent in your configuration settings for us to add to our continuous integration system? Do it today!!
Are you a customer that has a unique use case for wolfSSL? Feel free to submit some simple sample code that is similar to how you use it in your product. We will be more than happy to consider it for conversion into a test and get it running on our testing rig. Take control of your destiny for future updates of our products!!
Please reach out to support@wolfSSL.com to get the process started!
If you have questions about any of the above, please contact us at facts@wolfSSL.com or call us at +1 425 45 8247.
Download wolfSSL Now
Weekly updates
Archives
- December 2024 (15)
- 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)