So, what’s new at wolfSSL? Take a look below to check out the most recent news.
Or sign up to receive weekly email notifications containing the latest news from wolfSSL.
In addition, wolfSSL now has a support-specific blog page dedicated to answering some of the more commonly received support questions.

wolfSSL’s OpenSSL Compatibility

As of this writing, wolfSSL, which is our small embedded SSL library, supports all of the most commonly used OpenSSL functions.  As time goes on, we are incrementally improving our OpenSSL compatibility. 
Our process for improvement is driven by two forces. 
Firstly, we respond to customer requirements.  Our customers migrate from OpenSSL to wolfSSL for a variety of reasons.  Some migrate to get support for a particular RTOS or embedded environment not supported by OpenSSL.  Others need to reduce the overall size of their application by using a smaller library.  There are also some that migrate because they are seeking commercial licensing and professional support. 
Secondly, we test the compatibility layer by building wolfSSL with other open source projects that currently use OpenSSL.  We simply see what breaks, and then we add the missing OpenSSL functions to fix it.  You can see a couple of these efforts available on our download page in the form of experimental versions of Lighttpd and StunnelContact us if you would like help compiling wolfSSL with Lighttpd or stunnel.  We’ll be happy to help!

wolfSSL embedded SSL library supports TLS 1.2

The wolfSSL embedded ssl library and Gnu TLS are the first SSL libraries to support the new TLS 1.2 standard.  The TLS specification can be found here:  The first browser to support TLS 1.2 is Opera.  It appears that TLS 1.2 support is also available in Windows 7, though not by default.  As of this writing support from other browsers  appears to be in the works. 

Why use TLS 1.2?  In a nutshell, enhanced security.  TLS 1.2 is less susceptible to MITM attacks, has stronger default security, and adds some additional flexibility for developers.

Are you using or evaluating wolfSSL’s TLS 1.2 support?  Let us have your feedback!  We would also love to know what extensions to the specification that you think we should support.

Announcing a beta test of Secure Memcache with wolfSSL

Hi!  We have embedded wolfSSL into Memcache and are now making it available to beta testers. 
There are no obligations for beta testers, so if you want to just review our changes to the source, that is fine.  The first beta will not include client libraries, and we currently don’t know which ones should be supported, so your feedback here is critical.  Let us know which Memcache clients to support.  Your vote counts!  We’ll work with beta testers to provide the client library they need.  Our ideal beta tester has a test rig where they can assess the performance of a wolfSSL secured Memcache versus a regular Memcache.  If community interest in the beta is strong, and feedback is positive, then we’ll submit a branch/patch of Memcache with wolfSSL to the main source tree.  Contact us at to receive the beta. 

Open Source has comparable security as well as faster remediation times and fewer potential backdoors than commercial or outsourced applications.

See the excellent blog post by Katie Serignese here:

Get the report from Veracode here:  Registration is not required to download the report.  The detailed report is an excellent document.

Windows Kernel Mode compatibility for wolfSSL

We`re considering adding Windows Kernel compatibility to wolfSSL. This means that our embedded SSL library would run in Kernel mode and use either TDI or WinSocK Kernel. We`re not sure at this point whether we should use TDI or WinSocK Kernel. The advantage of this project may include performance enhancement for device driver implementers that want SSL security. Frankly speaking, we`re not sure if there will be other advantages and would love feedback on the general usefulness of this idea. Do Kernel developers want an SSL library? Please comment!

wolfSSL Release 1.5.0

A new release of wolfSSL embedded SSL library is now available for download.

Release 1.5.0 contains bug fixes, support for the GoAhead web server, sniffer support, and swig interface support for Python, Java, Perl, and others. Please see the README for more details. Public announcement is at PrWeb

yaSSL Release 1.9.9

A new release of yaSSL is now available for download.

Release 1.9.9 contains bug fixes, a potential security problem fix for a buffer overflow possibility in certificate name processing, and removal of assert()s.

wolfSSL Embedded SSL Release 1.3.0

A new release of the wolfSSL embedded SSL library is now available for download.
Release 1.3.0 contains bug fixes, a potential security problem fix, better support for porting, removal of assert()s, and a complete port to the THREADX operating system.
yaSSL/CaySSL have no renegotiaton vulnerability

yaSSL/wolfSSL have no renegotiaton vulnerability

Hi! We`ve been getting a number of questions about the high profile vulnerabilities in OpenSSL, GnuTLS, NSS and mod_ssl.
This vulnerability is based on a potentially insecure SSL early feature that yaSSL chose to never support in the first place. As such, yaSSL/wolfSSL was never insecure.

More details on the issue can be found below: From CVE

“The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a “plaintext injection” attack, aka the “Project Mogul” issue.”

Posts navigation

1 2 3 132 133 134 135 136

Weekly updates


Latest Tweets