RECENT BLOG NEWS
Fix for change to OBJ sn2nid behavior in wolfCLU
This PR updates wolfCLU to properly handle X509 name parsing following changes in wolfSSL’s OBJ_sn2nid function behavior. The changes focus on how Distinguished Name (DN) components are processed when creating X509 certificates.
These changes ensure wolfCLU properly handles X509 name components when interfacing with wolfSSL’s updated OBJ_sn2nid implementation.
Users working with X509 certificates through wolfCLU will benefit from more reliable DN parsing, particularly when using our OpenSSL compatibility layer. The changes maintain backward compatibility while supporting proper object identifier handling.
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
Our Post-Quantum Value Proposition
Research-focused cryptography startups deserve a lot of credit for the innovative work they do. They enrich the community and introduce solutions that may become crucial in the future. But their expertise is largely theoretical and academic, not practical and customer-aligned. wolfSSL, in contrast, is staffed by dedicated engineers with decades of experience delivering production quality solutions for critical infrastructure, crafting performant and portable code, often on short notice, for dozens of commercially significant architectures.
Given these hard-won advantages at wolfSSL, some cryptography providers have tried to differentiate themselves with custom hardware, promising a performance boost. Let’s test that proposition with a look at performance on lattice cryptography. The software implementation we’ll show is wolfSSL software production release 5.7.6, throughput per core on a commodity high performance CPU, in this case an AMD 7960X. The hardware-accelerated implementation we’ll show is PQShield’s PQPerform-Lattice, in a pre-production realization on Xilinx Zynq UltraScale+ at 322 MHz (see https://doi.org/10.1145/3689939.3695785).
Algorithm | key | operation | ops/sec | cycles/op | ops/sec | cycles/op |
size | wolfSSL | wolfSSL | PQShield | PQShield | ||
KYBER512 | 128 | key gen | 422907 | 9955.0 | 140000 | 2300 |
KYBER512 | 128 | encap | 231528 | 18184.5 | 100625 | 3200 |
KYBER512 | 128 | decap | 230252 | 18225.0 | 68511 | 4700 |
Even when application-specific proprietary silicon has a performance advantage–which PQShield’s pre-production FPGA realization does not–it complicates platform design and production timelines, introduces supply-chain vulnerabilities, increases BoM expenses, and complicates parallelization. And crucially, it restricts crypto-agility, given hardware resources that are specific to a narrow class of cryptographic algorithm. This matters. It is widely acknowledged that Kyber/ML-KEM is based on a fairly new and under-studied body of mathematics, and further investigation may yet uncover a fatal flaw in this, or any of the other novel algorithms working their way through the standards-making process.
wolfSSL demonstrates superior performance with an open source software solution, without tying your design to a particular class of cryptographic algorithm. Indeed, our latest software implementation of ML-KEM is even faster than pre-standardization Kyber, attaining well over 300k encapsulation and decapsulation ops/s per core on the CPU shown above.
When you work with wolfSSL, your priorities become our priorities. We have always focused our resources on development, guided and enabled by our proud history of organic growth and customer-centric philosophy.
We provide the best tested code, worldwide 24×7 technical support that is second to none, and on-site interactions to ensure your goals are met. Our technical prowess and decades of experience let us operate across the whole spectrum of runtimes, from bare metal microcontrollers to data center big iron, with hand-crafted assembly optimizations fully leveraging vector instruction extensions.
Beyond the technical dimension, the professionals at wolfSSL focus on making sure you fully understand your options for licensing, support, and consulting, tailoring plans for your specific requirements and preferences. We draw up NDAs, SOWs and legal contracts so that you as a business have everything you need to secure your operational necessities.
Our team will see your project through, not only to delivery, but for the entire lifecycle after delivery. We are your reliable partner through the entire process, laser-focused on delivered results. This is what we do, and we do it better than anyone. This makes wolfSSL your ideal partner as you embark on the transition to quantum-resistant cryptography.
If you have questions about any of the above, please contact us at facts@wolfssl.com or +1 425 245 8247.
Download wolfSSL Now
curl Distro Discussion 2025 – Save The Date
Join the second annual curl Distro Discussion on April 10th at 3 PM UTC (5 PM CEST). This online event brings together Linux and BSD distributions, OS maintainers, and the curl community for an in-depth two-hour conference. The event is free and open to anyone interested in improving curl’s integration within operating systems and package distributions.
Join us: curl Distro Discussion 2025
Date: April 10th | 3 PM UTC (5 PM CEST)
This is a unique opportunity for curl developers, maintainers, and distributors to discuss important aspects of curl deployment across various operating systems. Our goal is to make curl more efficient and secure within distributions.
Key discussion topics include:
- Enhancing curl’s build system, third-party library, and documentation for distributors
- Strategies to streamline security advisories and patch management
- Discussion on HTTP/3, long-term support, and TLS advancements
- Exploring Post-Quantum Cryptography in curl
- The future of wcurl and trurl
And more…
Feel free to add your own proposed discussion topics and sign up as an intended participant. Mark your calendar for April 10th at 3 PM UTC (5 PM CEST) and be part of shaping curl’s future in distributions and secure networking.
Check out the details of curl Distro Discussion 2025, and share this invitation with others in the open-source and security communities to help spread the word and ensure the right people are invited.
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
wolfSSL Enhances DTLS with Easier Connection ID Handling and Stateless Support
wolfSSL is continuously improving its support for DTLS (Datagram Transport Layer Security) to make it easier for developers to handle connection IDs and implement stateless DTLS services. In this blog post, we’ll explore the new APIs introduced in wolfSSL 5.7.6 that simplify these tasks.
DTLS is a variant of TLS designed for datagram-based transports like UDP. It’s widely used in IoT and real-time applications where packet loss and reordering are common. Connection IDs allow to tag each connection so that they can be maintained despite network changes, reducing rehandshake frequency and enhancing security with features like encrypted record types and padding for privacy. The wolfSSL stack allows the server to establish new connections in a stateless manner by not allocating any extra resources until the client can prove that they can reply to server packets. Managing CIDs and stateless operations can be challenging, but wolfSSL has introduced new features to streamline this process.
Demultiplexing DTLS messages for a server involves distinguishing between multiple client connections using a single socket. When data arrives on the socket, the server reads the packet and extracts the source IP address, port, and the connection ID. This information is then used to search through a list of active connections, matching the incoming packet’s source details with existing connections. The matching is done either based on the source address of the received datagram or on the CID found in the message itself. If a match is found, the data is processed by that connection. If no match is found, it attempts to establish a new connection. This method ensures each packet is correctly routed to its respective connection, allowing multiple clients to communicate over a single socket efficiently without dropping any packet.
wolfDTLS_accept_stateless
This function allows accepting DTLS connections in a stateless manner. It’s designed to use a single WOLFSSL object to listen to all new connections and indicate to the user when the WOLFSSL object has entered stateful handling and should no longer be used for new connections.
Example:
WOLFSSL* ssl; do { rc = wolfDTLS_accept_stateless(ssl); if (rc == WOLFSSL_FATAL_ERROR) { /* re-allocate the ssl object with wolfSSL_free() and wolfSSL_new() */ } } while (rc != WOLFSSL_SUCCESS); rc = wolfSSL_accept(ssl); if (rc != SSL_SUCCESS) { /* Handle error */ }
wolfSSL_inject
The `wolfSSL_inject` function allows you to inject application data directly into the WOLFSSL object, bypassing the usual IO calls. This is useful when data needs to be read from a single place and demultiplexed into multiple connections. The caller should then call wolfSSL_read() to extract the plaintext data from the WOLFSSL object.
Example:
int rc; WOLFSSL* ssl; byte data[2000]; sz = recv(fd, data, sizeof(data), 0); if (sz <= 0) { /* Handle error */ } /* Inject received data */ rc = wolfSSL_inject(ssl, data, sz); if (rc != WOLFSSL_SUCCESS) { /* Handle error */ }
wolfSSL_dtls_set_pending_peer
This function is introduced to handle the peer address when using Connection IDs. It sets a pending peer that will be upgraded to a regular peer when the next record is successfully de-protected. This should be used with Connection ID's to allow seamless and safe transition to a new peer address. This function can be called for every incoming datagram or when an address change is detected.
Example:
WOLFSSL* ssl; sockaddr_in addr; rc = wolfSSL_dtls_set_pending_peer(ssl, &addr, sizeof(addr)); if (rc != WOLFSSL_SUCCESS) { /* Handle error */ }
wolfSSL_is_stateful
This function checks if the current SSL session is stateful. This can be useful for determining whether the listening WOLFSSL object is still waiting to be associated with a single peer or if it has already progressed to handling a single connection.
Example:
WOLFSSL* ssl; byte isStateful; rc = wolfSSL_accept(ssl); /* rc might indicate failure when using non-blocking sockets */ if (wolfSSL_is_stateful(ssl)) { /* Session is stateful */ } else { /* Session is stateless */ }
wolfSSL_dtls_cid_parse
This function parses a CID from a DTLS message. This is useful for extracting and handling connection IDs in your application.
Example:
WOLFSSL* ssl; /* DTLS 1.2 app data containing CID */ byte cid12[] = "\x19\xfe\xfd\x00\x01\x00\x00\x00\x00\x00\x01\x77\xa3\x79\x34\xb3" \ "\xf1\x1f\x34\x00\x1f\xdb\x8c\x28\x25\x9f\xe1\x02\x26\x77\x1c\x3a" \ "\x50\x1b\x50\x99\xd0\xb5\x20\xd8\x2c\x2e\xaa\x36\x36\xe0\xb7\xb7" \ "\xf7\x7d\xff\xb0"; size_t cid_len = 8; const unsigned char* cid = wolfSSL_dtls_cid_parse(cid12, sizeof(cid12), cid_len); if (cid == NULL) { /* Handle missing CID */ }
wolfSSL_SSLDisableRead and wolfSSL_SSLEnableRead
These functions allow you to control the reading of data from the IO layer. `wolfSSL_SSLDisableRead` disables read operations, while `wolfSSL_SSLEnableRead` re-enables them.
Example:
WOLFSSL* ssl; /* Disable reading */ wolfSSL_SSLDisableRead(ssl); /* Perform some operations */ /* Re-enable reading */ wolfSSL_SSLEnableRead(ssl);
These new APIs in wolfSSL make handling DTLS connection IDs and implementing stateless services easier and more efficient. By providing direct data injection, pending peer management, state checks, and read control, wolfSSL continues to enhance its support for secure datagram-based communications. For more information about new and existing API visit our manual and take a look at our examples.
If you have questions about any of the above, please contact us at facts@wolfSSL.com or +1 425 245 8247.
Download wolfSSL Now
wolfSSL at Embedded World 2025: Pioneering Advanced Cryptographic Solutions
Secure your Embedded Projects with wolfSSL, the Leader in Advanced Cryptographic Protocols
wolfSSL is returning to the Embedded World Exposition and Conference in 2025, bringing the best-tested cryptography and industry-leading security solutions for embedded systems.
Join us March 11th – 13th in Nuremberg, Germany. Visit Hall 4, Booth #4-201a to explore how wolfSSL’s advanced cryptographic protocols and open-source cybersecurity solutions can safeguard your embedded projects.
Schedule a one-on-one meeting with our cryptography experts – email us at facts@wolfssl.com to book a meeting.
With over 5 billion secured connections, wolfSSL continues to set the standard for embedded security. Backed by the largest cryptography-focused engineering team, our solutions ensure seamless integration, maximum efficiency, and future-proof security across industries. Get started today: wolfssl.com/download.
Live Demos at Embedded World 2025
Join us at Hall 4, Booth #4-201a, and partner booths to see live demonstrations showcasing secure boot, post-quantum cryptography, TLS acceleration, and more.
- Demo 1: Launching Safe and Secure Systems with Intel, Curtiss Wright, wolfSSL and SYSGO
Location: Hall 4, Booth #4-201aSecure boot is essential for mission-critical systems. This demo highlights wolfBoot integrated with wolfCrypt, running on Curtiss-Wright’s VPX3-1262 SBC with 13th Gen Intel Core i7 and SYSGO PikeOS RTOS. See how DO-178C DAL-A certifiable wolfBoot and wolfCrypt protects avionics systems.
- Demo 2: wolfSSL and NXP / Infineon
Location: Hall 4, Booth #4-201aPower up your embedded security with wolfSSL (TLS), wolfMQTT, wolfSSH, and wolfTPM on NXP FRDM-MCXN947 (Cortex-M33, 150MHz) with Infineon SLB9673 TPM 2.0, ensuring secure communication and authentication. Also, explore wolfBoot on NXP FRDM-MCXW71, designed for trusted firmware updates in resource-constrained environments.
- Demo 3: wolfSSL and ST
Location: Hall 4, Booth #4-201aOptimize security without compromising performance. Watch wolfCrypt and wolfSSL TLS benchmarks on ST32MP257F (Dual Cortex-A35 1.5GHz + Cortex-M33 400MHz) running OpenSTLinux. This demo demonstrates how wolfSSL’s cryptographic library accelerates encryption speed, reduces resource consumption, and ensures ultra-low latency for TLS handshakes.
- Demo 4: wolfSSL and Winbond
Location: Hall 4A, Booth #4A-635Future-proof your firmware security with wolfCrypt Post-Quantum LMS. This demo features Winbond W77Q Secure Flash on Raspberry Pi Zero over SPI, demonstrating quantum-resistant firmware updates to protect devices from emerging cyber threats.
Why Choose wolfSSL for Embedded Security?
- Lightweight and Fast: Written in C, wolfSSL boasts a compact footprint, up to 20 times smaller than OpenSSL, minimizing memory usage and maximizing performance on even the most resource-constrained microcontrollers and processors. Integrated robust security into your embedded systems without sacrificing functionality or performance.
- Industry Leading TLS 1.3 and DTLS 1.3 Support: As the first commercial implementation of TLS 1.3, we offer the most up-to-date security protocols, keeping your data secure with the latest standards.
- Comprehensive Hardware Integration: wolfSSL supports a wide range of hardware cryptography schemes, including Intel AES-NI, ARMv8, and various secure elements like NXP SE050 and Microchip ATECC, providing enhanced security and performance. Check out the every hardware cryptography scheme wolfSSL has ever enabled.
- Rigorous Testing and Certification: Our solutions are best-tested and come with incomparable certifications, including FIPS 140-3 validated certificate (#4718), ensuring they meet stringent security standards.
- Dedicated Support: We offer 24/7 support from our team of engineers, ensuring you receive immediate assistance whenever you need it.
Connect with wolfSSL at Embedded World 2025
Don’t miss the chance to see wolfSSL in action! Visit us at Hall 4 Booth #4-201a to explore our cutting-edge cryptographic solutions and live demos. Want a personalized discussion? Email us at facts@wolfssl.com to schedule a one-on-one meeting with our experts. See you in Nuremberg!
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
Partner Webinar: How AI-Automated Fuzzing Uncovered a Vulnerability in wolfSSL
Despite wolfSSL’s rigorous software testing practices, in October 2024, Code Intelligence—an application security vendor—discovered a potentially exploitable defect in wolfSSL. Remarkably, the potential vulnerability was found without human intervention. The only manual step was executing a single command to trigger autonomous fuzz testing.
Join wolfSSL and Code Intelligence for a live webinar featuring a real-time demo of AI-driven fuzz testing and an in-depth analysis of a heap-based use-after-free vulnerability in wolfSSL.
Register now: How AI-Automated Fuzzing Uncovered a Vulnerability in wolfSSL
Date: February 26th | 9 AM PT / 6 PM CET
This webinar will cover:
- Discover how wolfSSL tests its code to ensure quality and security.
- Learn how AI-automated fuzz testing works and how it autonomously found the vulnerability.
- Watch a live demo of AI-automated fuzz testing on wolfSSL’s libraries.
Register now and be the first to see how AI-driven security testing is shaping the future!
As always, our webinar will include Q&A 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
wolfSSH 1.4.20: Enhanced Features and Stability
The wolfSSL team has released wolfSSH version 1.4.20, introducing some new features and nice fixes!
New Features:
- DH Group 16 and HMAC-SHA2-512 Support: This addition gives more options for algorithms used when connecting and more interoperability with other implementations.
- Keyboard-Interactive Authentication: Providing a more versatile authentication method implementing RFC 4256.
Enhancements and Fixes:
- Memory Management Improvements: wolfSSH now handles memory more efficiently, particularly in RNG initialization and the SCP example, ensuring cleaner resource management.
- Stability Enhancements: Updates to wolfSSHd include better handling of failures and connections, making the server more robust and reliable.
- Resolved Issues: Fixes address SFTP compilation problems with WOLFSSH_FATFS and simplify the autogen script for easier integration.
Check out the ChangeLog for a full list of features and fixes.
Stay updated with wolfSSH for ongoing enhancements! 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
Deprecation Notice: ARC4
The wolfSSL team is announcing the deprecation of the ARC4 cipher. This decision is part of our ongoing effort to simplify the wolfSSL codebase and focus on supporting the most secure and widely-used ciphers.
The ARC4 cipher has been shown to have significant weaknesses, including:
- Key biases and correlations
- Plaintext recovery attacks
- Increased risk of data breaches
Removing ARC4 will allow us to reduce the complexity of our codebase and devote more resources to maintaining and improving our supported ciphers.
Recommendations:
- Begin transitioning away from ARC4 and towards more secure ciphers, such as AES or ChaCha20.
- Consult the wolfSSL documentation and support resources for guidance on migrating away from ARC4.
We will provide additional information on the removal timeline in the future. If you have any questions or concerns about this deprecation, please don’t hesitate to reach out to the wolfSSL support team.
If you have questions about any of the above, please contact us at facts@wolfSSL.com or +1 425 245 8247.
Download wolfSSL Now
wolfMQTT Releases v1.19.2
In the realm of lightweight MQTT (Message Queuing Telemetry Transport) implementations, wolfMQTT maintains its commitment to reliability and performance. With the release of version 1.19.2, wolfMQTT strengthens its core functionality through targeted improvements and enhanced testing infrastructure.
Key Improvements:
- Enhanced Connection Reliability
The implementation of improved error handling in the “mqttsimple” client ensures more robust connection management, particularly beneficial for embedded applications where connection stability is crucial. - Optimized Keep-Alive Mechanism
A significant enhancement to the ping response handling improves the reliability of MQTT keep-alive functionality, ensuring more stable long-term connections and better resource management. - Strengthened Testing Infrastructure
- Modernized continuous integration workflow with Ubuntu 22.04
- Enhanced artifact testing procedures for more comprehensive quality assurance
- Improved Zephyr platform compatibility through targeted build fixes
Release 1.19.2 has been developed according to wolfSSL’s development and QA process and successfully passed the quality criteria.
Check out the ChangeLog for a full list of features and fixes, or contact us at facts@wolfssl.com with any questions.
While you’re there, show us some love and give the wolfMQTT project a Star!
You can download the latest wolfMQTT release from our website or clone directly from our GitHub repository.
If you have questions about any of the above, please contact us at facts@wolfSSL.com or +1 425 245 8247.
Download wolfSSL Now
Using wolfCLU To Verify a Certificate Chain of More than 2 Certificates
With the release of wolfCLU 0.1.7, you can now verify long certificate chains! Our way of doing it is a bit unique.
You will need to verify the certificates in your chain one by one. For example, suppose you have a certificate chain where there is a root, intermediate, another intermediate and leaf certificate. If they are named first.pem, second.pem, third.pem and fourth.pem you will need to verify like this:
$ ./wolfssl verify -CAfile first.pem second.pem $ ./wolfssl verify -partial_chain -CAfile second.pem third.pem $ ./wolfssl verify -partial_chain -CAfile third.pem fourth.pem
This will work for short chains as well as long chains.
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
Weekly updates
Archives
- March 2025 (21)
- February 2025 (21)
- January 2025 (23)
- 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)