Category: Uncategorized

MD5 Disabled by Default in wolfSSL: What You Need to Know

As part of our ongoing effort to deliver secure-by-default cryptography, wolfSSL has disabled the MD5 hash algorithm by default in the latest release. Don’t worry, it isn’t going away completely, but just disabled at compile time, by default.

Why Disable MD5?

MD5 has been considered cryptographically broken for many years due to known collision attacks. While it’s still used in legacy systems for non-security-critical purposes, it no longer meets modern security standards. Disabling MD5 by default aligns wolfSSL with best practices and further hardens applications that rely on us for secure communications, and has already been done in FIPS builds of wolfSSL.

What Changed?

MD5 is now disabled by default in the master branch of wolfSSL. We expect this default behavior to be in release 5.8.2 and up. If your application or any third-party dependency attempts to use MD5 without explicitly enabling it, you may encounter build or runtime issues such as:

  • Compilation errors involving wc_InitMd5() or other MD5 functions
  • Protocol negotiation failures if MD5 is assumed as a supported digest (e.g., in TLS 1.0/1.1 or some legacy certificate chains)
  • Unexpected behavior in libraries that rely on MD5 internally but don’t check if it’s available

You can check if MD5 is disabled in your configuration by seeing if NO_MD5 is set at compile time.

How to Re-Enable MD5 (If Needed)

If you’re working in a legacy environment or need MD5 for interoperability reasons, you can explicitly re-enable MD5 support by doing the following.

Builds using autotools:

./configure --enable-md5

Builds using cmake:

mkdir -p build
cd build
cmake .. -DNO_MD5=OFF

We strongly encourage you to audit any use of MD5 in your project before re-enabling it. If it’s being used for digital signatures or certificate verification, consider updating to SHA-256 or stronger algorithms.

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: How to Determine FIPS Compliance for Government Buyers

Cut through the confusion of FIPS 140-3 compliance and learn how to verify it with confidence.

Join us on August 6th at 9 AM PT for a focused webinar presented by wolfSSL Senior Software Engineer Kaleb Himes. This session will break down the complexity of FIPS?140?3 compliance and help government buyers and contributors accurately evaluate solutions.

Register today: How to Determine FIPS Compliance for Government Buyers
Date: August 6th | 9 AM PT

wolfSSL maintains FIPS 140-3 validated certificate #4718 and #5401 and brings unmatched portability, running on everything and well optimized for dozens of Hardware targets. In this webinar, we will walk through exactly how to verify FIPS compliance and avoid common mistakes when reviewing vendor claims.

This webinar will cover:

  • Key FIPS terms and why FIPS matters
  • Why it’s important for your Operating Environment (OE) to appear on the certificate
  • How to looking up and interpret a FIPS certificate (SP800-140Br1 automated FIPS certs vs traditional FIPS certs included)
  • How to locate and read the module’s Security Policy
  • How to determine if an OE was actually tested or only vendor affirmed (SP800-140Br1 vs traditional included)
  • How to check algorithm (CAVP) certificates
  • How to spot fake or misleading FIPS claims

Register today and gain a clear understanding of how to assess FIPS compliance before making procurement decisions.

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

A2A and wolfSSL

Here at wolfSSL, we are seeing a lot of interest in AI. Some of the most fascinating developments that are happening are around letting different AI agents communicate with each other. Do those communications need to be secured, authenticated, and integrity checked? Of course!

Enter the A2A (Agent2Agent) protocol, which uses HTTPS as its primary transport layer.

Check out the official A2A protocol implementation links:

How can wolfSSL help in this endeavor? Well, it is looking like the government is going to be one of the biggest consumers of AI technology, with a fast and agile uptake of AI technology. If they are going to need cryptography to protect this protocol, it had better be FIPS 140-3 certified! Did we mention our FIPS 140-3 certificate #4718?

This shows the chain of dependencies from the A2A reference library down to the OpenSSL library, which provides the underlying cryptographic functionality:

A2A Reference Library → httpx → httpcore → ssl (Python module) → OpenSSL

We can add wolfProvider and wolfCrypt FIPS to that to bring it into compliance so the government can use it! It would look like this:

A2A Reference Library → httpx → httpcore → ssl (Python module) → OpenSSL → wolfProvider → wolfCrypt FIPS

For extra performance, another option would be to do an integration with wolfssl-py; our python wrapper for wolfSSL.

Interested in seeing this happen? We are! Let us know if you’re interested!

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 Expands Embedded Security with HighTec Compiler and RTOS Support

The embedded systems landscape continues to evolve rapidly, with developers demanding robust security solutions that seamlessly integrate with their preferred development tools and real-time operating systems. Today, we’re excited to announce that wolfSSL’s comprehensive security suite will support the HighTec compiler and RTOS, bringing enterprise-grade cryptographic capabilities to even more embedded applications.

Comprehensive Security for HighTec Environments

This new support will encompass our complete security ecosystem:

  • wolfSSL – Our flagship TLS/SSL library can compile cleanly with HighTec’s advanced optimization features, ensuring minimal memory footprint while maintaining maximum security. Whether you’re building IoT devices, industrial controllers, or automotive systems, wolfSSL delivers the cryptographic protocols you need with the performance HighTec users expect.
  • wolfBoot – Secure boot has never been more critical for embedded systems. Our wolfBoot secure bootloader will integrate seamlessly with HighTec-compiled applications, providing verified boot processes that protect against firmware tampering and ensure only authenticated code executes on your devices. The combination of HighTec’s efficient code generation and wolfBoot’s security features creates a powerful foundation for trustworthy embedded systems.
  • wolfHSM – Hardware Security Module functionality comes to HighTec environments through wolfHSM, enabling secure key storage, cryptographic operations, and hardware-based root of trust. This integration will allow developers to leverage dedicated security hardware while maintaining the development workflow they know and trust.

Why This Matters

The HighTec compiler family has long been trusted by embedded developers for its superior code optimization and comprehensive target support. By adding native wolfSSL support, we’re eliminating the integration barriers that previously required custom porting efforts. This means:

  • Faster Time to Market: No more wrestling with compiler-specific adaptations
  • Optimized Performance: HighTec’s advanced optimizations will work seamlessly with our security libraries
  • Reduced Risk: Proven security implementations without the uncertainty of custom ports
  • Future-Proof: Ongoing support ensures compatibility with future HighTec releases

Real-World Impact

Consider an industrial automation system running on a HighTec-supported microcontroller. With this new support, developers can now implement:

  • Secure communication channels using wolfSSL’s TLS 1.3 implementation
  • Verified boot sequences through wolfBoot integration
  • Hardware-backed key management via wolfHSM

All while leveraging HighTec’s industry-leading code optimization and debugging capabilities.

Looking Forward

This expansion represents more than just another compiler target – it’s part of our ongoing commitment to making robust security accessible across the entire embedded ecosystem. As embedded systems become increasingly connected and critical to our daily lives, having trusted security solutions that work with your preferred tools becomes essential.

The combination of HighTec’s development excellence and wolfSSL’s security expertise opens new possibilities for secure embedded applications. Whether you’re protecting industrial control systems, securing IoT deployments, or building the next generation of connected devices, this integration provides the foundation you need.

Ready to explore what wolfSSL can do in your HighTec environment? Contact our team to learn more about implementation strategies, performance optimizations, and best practices for your specific use case.

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

wolfCrypt FIPS 140-3 Certificate #5041 Now Validated

We’re proud to announce that our copy of wolfCrypt has officially again received FIPS 140-3 validation, listed under certificate #5041, posted on July 18, 2025 by NIST. This validation reflects our continued commitment to building secure, standards-compliant products using rigorously tested cryptography.

This FIPS 140-3 version of wolfCrypt improves on the earlier 140-2 validation in several key ways:

  • Faster boot times: Self-tests are deferred until the first use of each algorithm, rather than running all at startup.
  • Optimized for embedded systems: Minimal footprint, low power consumption, and efficient performance for real-time and resource-constrained environments.
  • Expanded algorithm support, including:
    • AES-OFB mode
    • RSA 3072, 4096, and PSS
    • TLS 1.2 and TLS 1.3 key derivation functions (KDF)
    • SSH KDF
  • New degraded mode: If an algorithm self-test fails, others can remain available, improving system resilience.

We selected Acumen Security as our FIPS lab partner for this effort and sincerely appreciate their professionalism and expertise throughout the validation process.

wolfCrypt’s FIPS-validated module can be used as a drop-in OpenSSL engine or provider, making it easy to integrate into existing applications. It’s ideally suited for embedded use cases like secure networking, medical devices, and industrial control systems.

Certificate #5041 offers all the same algorithms as certificate #4718, but will sunset on July 17, 2030. After that, continued use will require revalidation or transition to a newer certificate.

To learn more about FIPS 140-3 and the transition from 140-2, wolfSSL has published helpful resources:

For questions or integration support for FIPS, contact us at fips@wolfssl.com

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

wolfCLU 0.1.9 Available Now

wolfCLU version 0.1.9 is now available! This command-line utility, built on the wolfSSL embedded TLS library, helps with admin tasks and common use cases such as key generation and certificate parsing to human human-readable form.

Among the most notable changes to this release is the addition of support for PKCS8 and Base64 commands, introduced in PR #178. These features make it easier to handle common encoding formats and key conversions directly from the command line, streamlining workflows involving PEM or DER-encoded data.

The update also includes important fixes to macro definitions related to client and server Key Encapsulation Mechanisms (KEM), as noted in PR #177. These corrections ensure proper configuration and usage when working with post-quantum cryptographic modes and hybrid TLS key exchange scenarios.

To support users working in FIPS-approved environments, wolfCLU now better aligns with FIPS 140-3 expectations. In PR #183, tests were adjusted to reflect the removal of DES in FIPS mode, and new output was added to indicate when FIPS is enabled. These changes help clarify operational state and support auditability during validation efforts.

This release also updates the license from GPLv2 to GPLv3 (PR #184).

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

What We Talk About When We Talk About Support

Here at wolfSSL, we are usually very humble about how we help our customers. Today, that ends as we go loud and proud, letting you know what our customers are saying about our technical support!

“Super fast and helpful support. Was able to help quickly unblock my progress.”

– Top 5 Prime Government Contractor

“I sincerely appreciate your outstanding support in resolving the HTTPS implementation challenges with WolfSSL. Your expertise, prompt responses, and clear guidance were invaluable in addressing certificate handling, configuration, and performance optimizations. Thanks to your help, WolfSSL is now functioning perfectly in our system. With this issue fully resolved, I am marking the ticket as solved. Your dedication and professionalism made a significant difference, thank you for your patience and support!”

– Medical Devices Subcontractor

“It was great to know the support extended by the team to answer all our queries. We had good interaction with Rich and Antony on the coming integration of wolfSSL with our product.”

– European Manufacturing Automation Company

“Very quick, very friendly and very helpful – thanks!”

– German Car Sharing Pioneer

“Support is much appreciated, got the work around very quick and it was useful.”

– Emergency First Responder Communications Equipment Manufacturer

“This was great; a lot of work by David G. and Eric B. It involved hearing our issue, providing suggestions, looking through our code, providing solutions. Solutions provided ended up being exactly what we needed. Thanks for all your help!”

– Aerospace, Healthcare and Industrial Industry Technology Integrator

“I want to sincerely thank the wolfSSL support team for their excellent, insightful, and patient assistance throughout my recent experience. I was working on a complex FIPS-Ready build for Apple Silicon (M1/M2), and ran into several architecture-specific challenges involving ASM optimizations, test suite errors, and toolchain compatibility on macOS. The wolfSSL team — especially Kaleb and others — went above and beyond to help me troubleshoot the issues, offering not only technical solutions, but also clear explanations behind them. Their responsiveness, deep knowledge, and willingness to guide me through each step (including subtle configuration and environment nuances) made a huge difference. Thanks to their support, I was able to successfully build, test, and benchmark wolfSSL in my development environment. It’s rare to find a support team that’s this technically strong and genuinely helpful. Hats off to wolfSSL — you’ve earned my respect and recommendation.”

– Academic Research Institution

“First class support. Fast, reliable!”

– Top Tier European Satellite Vendor

“Bill has excellent knowledge about wolfHSM. Really satisfied with his responses and help. Great to work with Bill.”

– Tier 1 Big 3 Automotive Subcontractor

“Kareem was super helpful. He worked with me through all the issues that I had and kept after it throughout all my questions. I really appreciate his knowledge and ability to help me get the answers.”

– American Cloud Collaboration Software Company

“The bug fix was pulled into the master branch within 2 hours of reporting it. Can’t get much faster than that!”

– Largest American Medical Devices Manufacturer

“I am very happy with the support I got and I was able to resolve the issue. Marco has answered all the questions I had and I am very satisfied with the technical support. Thank you.”

– German Academic Post-Graduate Institution

“I was very satisfied with the support I received. The answers were prompt and very detailed. Thanks!”

– Top Tier German Aerospace Company

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: Everything You Need to Know About Automotive Cybersecurity – Tailored for the Asia-Pacific Time Zone

Strengthen your vehicle’s defenses with proven cybersecurity solutions.

Join us on July 31 at 5 PM PT / August 1 at 9 AM JST for a live automotive cybersecurity webinar, “Everything You Need to Know About Automotive Cybersecurity,” presented by Senior Software Engineer Eric Blankenhorn. This session explores the growing need for secure, connected, and software-defined vehicles. You’ll learn about wolfSSL’s approach to automotive cybersecurity, backed by real-world examples and practical integration strategies.

Register Now: Everything You Need to Know About Automotive Cybersecurity – Tailored for the Asia-Pacific Time Zone
Date: July 30 | 5 PM PT / Aug 1 | 9 AM JST
(This webinar is tailored for the Asia-Pacific Time Zone)

wolfSSL is a trusted provider of automotive-grade cybersecurity used by leading OEMs and Tier 1 suppliers. A key focus of this webinar is wolfHSM, our Hardware Security Module framework. Designed to support automotive-grade requirements, including AUTOSAR, PKCS11, and SHE, wolfHSM enables secure key storage, cryptographic operations, and secure boot, all while meeting the strict performance and safety demands of embedded automotive systems.

This webinar will cover:

  • How wolfSSL supports modern automotive cybersecurity across global markets
  • What sets wolfHSM apart, and why it’s ideal for embedded applications
  • Best practices for implementing secure firmware updates in vehicles
  • How TLS 1.3 enables safe communication from the vehicle to the cloud
  • Approaches to securing ADAS and autonomous driving systems
  • Real-world guidance on running TLS over CAN
  • How wolfSSL ensures the highest code quality through industry-leading test coverage and validation

Register now to gain practical insights into securing next-generation automotive systems with wolfSSL!

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

Live Webinar: Cybersecurity Solutions for the Satellite Industry

Secure satellite communication and boot integrity with wolfSSL: FIPS 140-3, Post-Quantum, and Embedded Optimization

Join us on July 30th at 9 AM PT for the ‘Cybersecurity Solutions for the Satellite Industry’ webinar. As the industry leader in space-grade cybersecurity, wolfSSL products are deployed across satellites, delivery / rocket systems, and ground stations. Our software provides lightweight cryptographic and (D)TLS solutions optimized for satellite and aerospace systems. wolfSSL solutions also feature robust quantum-resistant cryptography, FIPS 140-3 certification, and CNSA 2.0 compliance.

Register Now: Cybersecurity Solutions for the Satellite Industry
Date: July 30 | 9 AM PT

Learn about how our companion products, such as wolfBoot, wolfTPM, and our other open source libraries, can be used to secure satellites and related systems.

This webinar will cover key areas such as integration with embedded systems, cryptographic library optimization, securing high-value projects, and addressing specialized security requirements. You’ll gain insights into military use cases, including FIPS-compliant deployments for the U.S. military, Space Force, rocket systems, and safety-critical space stations, aligned with DO-178 certification requirements.

Register now to enhance your satellite missions with wolfSSL’s trusted, industry-leading cryptographic security.

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

Verifying TPM Endorsement Certificates with wolfTPM

We’re excited to share a new feature added to wolfTPM: a lightweight example for verifying TPM Endorsement Key (EK) Certificates without wolfCrypt.

The new example, `verify_ek_cert`, retrieves and verifies the EK certificate stored in the TPM’s non-volatile memory. This supports TPMs like the Infineon SLB9672/SLB9673, STMicro ST33 series, and validates their RSA-signed EK certs using the manufacturer’s public CA certificate. This is essential for secure boot, remote attestation, and provisioning in trusted systems.

Highlights:

  • Reads EK cert from NV memory (Index: 0x1C00002)
  • Parses and validates the X.509 certificate
  • Verifies hash and signature using CA public key
  • Confirms TPM identity and trustworthiness

This example uses minimal ASN.1 parsing to reduce code size and avoid dependencies on wolfCrypt. This approach is especially valuable for DO-178C certification efforts, where reducing complexity and traceability is critical. wolfTPM remains the only TPM 2.0 stack specifically designed for bare-metal environments with a minimal code footprint—ideal for embedded, safety-critical systems.

To try it:

$ git clone https://github.com/wolfSSL/wolfTPM.git
$ cd wolfTPM
$ ./configure --disable-wolfcrypt && make
$ ./examples/endorsement/verify_ek_cert

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

Posts navigation

1 2 3 4 … 206 207 208