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.”

yaSSL Embedded SSL Release 1.2.0

The wolfSSL embedded SSL library Release 1.2.0 is now available for download.
Release 1.2.0 for wolfSSL adds bug fixes and session negotiation when first use is read or write.
To get TLS 1.2 support please use the client and server functions:
SSL_METHOD *TLSv1_2_server_method(void);
SSL_METHOD *TLSv1_2_client_method(void);
The wolfSSL OpenSSL compatibility layer was tested against lighttpd 1.4.23, see the notes in README for build instructions. See the download page for a linux build of Lighty built with wolfSSL.  Let us know if you have any problems building wolfSSL with Lighty or if you need help building the wolfSSL/Lighty combination on another operating environment at info@yassl.com.