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.

Mark your calendar: February 8th | 10 am PT

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. Register today 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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!
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. Protocol Analysis: TLS-Attacker, a Java-based framework for analyzing TLS libraries, helps us analyze that wolfSSL correctly conforms to the SSL/TLS specification.
  15. 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.
  16. 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

Secure Embedded Systems with wolfSSL: Daniel Stenberg’s cURL Insights at FOSDEM 2024

Get ready to dive into a world of data transfer libraries with Daniel Stenberg, the founder of cURL, at FOSDEM 2024 on February 3rd and 4th in Brussels, Belgium

Daniel Stenberg, the driving force behind cURL, is a featured speaker at FOSDEM 2024 where he will deliver two presentations. The first presentation, “Broom not included: curling the modern way”, is scheduled for February 3rd at 10:50 am CET in Room UB5.230. The second presentation, “You too could have made curl!”, will take place on February 4th at 10 am CET in Room K1.105 (La Fontaine).

Explore the prowess of cURL and libcurl, widely recognized as premier data transfer libraries with URLs for developers. You can expect to gain comprehensive insights during the session, including technical updates, invaluable command lines, the trurl, recently created companion tool for URL manipulations and much more. Join this session to unlock the potential of cURL, elevating your technical skills to the next level. Don’t miss this chance to delve deep into cURL’s capabilities and enhance your skills!

Mark your calendar for insightful talks:

  1. Broom not included: curling the modern way
    • Date: February 3rd, 2024 at 10:50 am CET
    • Location: Room UB5.230
  2. You too could have made curl!
    • Date: February 4th, 2024 at 10 am CET
    • Location: Room K1.105(La Fontaine)

Find wolfSSL and cURL at Building K on level 1, Stand #3 in the IoT area. Daniel Stenberg will be available at stand #3 on February 3rd from 11:30 am to 1:00 pm and February 4th from 11:00 am to 1:00 pm to address your questions. Additionally, cURL and wolfSSL stickers will be available at the stand!

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: Secure and Reliable Firmware Updates with wolfBoot in 2024

Join us for a webinar on ‘Secure and Reliable Firmware Updates with wolfBoot,’ presented by wolfSSL Senior Engineer and security expert, Daniele on February 1st at 10 am PT.

Save the date: February 1st | 10 am PT

Explore the challenges associated with connected embedded systems that allow remote updates of various artifacts and how a secure boot mechanism emerges as a robust solution. In such systems, it is crucial to address security risks. Daniele will provide a comprehensive guide on securing embedded systems, emphasizing the importance of a secure boot mechanism and showcasing wolfBoot as a leading solution in the realm of firmware security.

Don’t miss out on this opportunity to learn the best solutions for securing your firmware. Daniele will take you through the possibilities of real-life secure firmware update solutions, designed using the latest standards and best cryptographic algorithms. Register now to secure your spot 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

Handshake Message Coalescing Vulnerability

wolfSSL prior to version 5.6.6 had a vulnerability where the (D)TLS key boundaries were not properly checked. As a result, it was possible to combine (D)TLS messages using different keys into one (D)TLS record. The most extreme edge case is that, in (D)TLS 1.3, it was possible that an unencrypted (D)TLS 1.3 record from the server containing first a ServerHello message and then the rest of the first server flight would be accepted by a wolfSSL client. In (D)TLS 1.3 the handshake is encrypted after the ServerHello but a wolfSSL client would accept an unencrypted flight from the server. This does not compromise key negotiation and authentication so it is assigned a low severity rating.

We would like to thank Johannes Wilson for the report (Sectra Communications and Linköping University). The fix for this issue is located in the following GitHub Pull Request: #7029.

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 v2.0.0 intel x86_64 support

wolfBoot v2.0.0 introduced support for the Intel x86-64 bit architecture by leveraging the Intel Firmware Support Package (Intel FSP) and several new exciting and interesting features: TPM integration, Multiboot2/ELF support, PCI support, AHCI support, SATA security features, and others.

On Intel x86_64, wolfBoot uses a dual stage design. In the first stage, It initializes the memory and the hardware with the help of Intel FSP. Intel FSP allows BIOS and bootloader developers to focus on the critical features and broad support without worrying about the hardware initialization details. After the memory and silicon initialization, wolfBoot enumerates and configures all PCI devices in the system.

In the second stage, when the hardware is up and ready, wolfBoot does the necessary steps to read, decrypt, verify, and safely boot the main application. We added support for AHCI controller, SATA disks and ATA security commands: the main application can now be stored in a password-locked hard drive!

In both stages, wolfBoot verifies each component loaded, either from system ROM or from the hard disk, plus the TPM support allows very interesting scenarios. First, it enables TPM-assisted measured boot: each component loaded into the system is “measured”, taking part in an integrity proof managed inside the TPM itself so that certain operations are allowed only if the system is in a trustful state. The TPM can store (“seal”) secrets that can be recovered (“unsealed”) only if the system is in a precise state. If compromised software is running on the target, the secret never leaves the TPM.

In wolfBoot we leverage this by sealing the disk password (randomly generated at the first boot) in the TPM and binding the unsealing to a precise state of the system. If the loaded components are compromised or if the disk is removed from the device for direct tampering, the disk can’t be unlocked at all!

Once the disk is unlocked, it’s time to load the application in the right place and communicate the current hardware situation before booting. wolfboot supports the Multiboot2 standards to communicate with the main application and it supports the Executable and Linkable Format (ELF) format, one of the most ubiquitous object file formats for binary distribution, to load the application in the right places into the memory. As it supports memory virtualization, the application can be loaded anywhere in the address space, even above the 4GB limit.

And, as always, all current features of wolfBoot such as verified boot, OTA firmware secure update with power-fail tolerance, delta updates, encrypted firmware, and post-quantum firmware verification, will be directly available on the Intel x86-64 architecture.

All these new features are supported on the VX3060 Kontron board and can be tested on QEMU, but new hardware will be supported soon. If you have a new Intel-based board you would like to have supported or for any other comments, feedback or questions, don’t hesitate to contact us at facts@wolfSSL.com or call us at +1 425 245 8247.

Download wolfSSL Now

Posts navigation

1 2 3 4 5 6 7 8 9 10 188 189 190