RECENT BLOG NEWS
yaSSL 2.0 is now available
yaSSL, the leading C++ based ssl library, is now available for download. This release of yaSSL contains bug fixes, new testing certs, and a security patch for a potential heap overflow on forged application data processing. Vulnerability discovered by Matthieu Bonetti from VUPEN Security (http://www.vupen.com).
yaSSL’s partnership with ARM
yaSSL has now been partnered with ARM for 18 months! Why is yaSSL partnered with ARM? Simply stated, because so many of our users and customers are running on the ARM chipset. Users choose wolfSSL on ARM because it is fast, lightweight, and easily embedded to secure connected application software. To meet the needs of our customers, we have ported the wolfSSL embedded ssl library to several ARM based environments, including Android, ThreadX, QNX, Ubuntu, IAR, MontaVista and OpenWRT. If you need wolfSSL on another ARM based operating environment that we don’t currently support, then contact us at info@yassl.com.
Benchmark for secure Memcache running the wolfSSL embedded SSL library
We recently announced a beta version of secure Memcache is available to the community. Users are excited about having SSL available in memcache, but show concern about the performance cost of enabling security. With this feedback in mind, we benchmarked secure memcache performance against standard memcache. See the graph below for comparison of secure memcache to standard memcache by measure of TPS. The first bar is regular memcache. The rest of the bars show secure memcache running with different cipher options. We’ve also included the performance of “direct to database,” or running without memcache at all, as a baseline for comparison.
We have several additional optimizations in the works that will bring the performance of secure memcache to within 5-10% of standard memcache for most environments, and can also provide network, operating system and hardware specific optimizations for specific users.
You will see from the graph that running Memcache with SSL enabled is 4x faster than running direct to database. The cost of running securely varies between about 25% and 40%, depending on cipher. There is some cost to running secure memcache, but it is not unbearable. Email us at facts@wolfssl.com if you want more details on the benchmark.
Who should use secure Memcache? Generally speaking, anyone concerned about the security of their memcache data.
More specifically:
1. Users with regulatory compliance requirements.
2. SaaS companies hosting sensitive customer and user data who cannot risk a breach that could damage their reputation
3. Users running in the cloud.
4. Users concerned with masking memcache data securely within their firewall.
Contact us at info@yassl.com if you are interested in receiving the beta or for more information.
wolfSSL embedded SSL for ThreadX
We have ported wolfSSL to the ThreadX operating environment! Our decision to invest in the porting process is based on strong customer demand for a small footprint, high performance, royalty free SSL library on ThreadX. ThreadX and wolfSSL have a lot in common. Both companies operate under similar business models, target similar usage profiles, and work with the same chip and board vendors. With regard to usage profile, both ThreadX and wolfSSL operate well in resource constrained environments and are popular with developers of today’s new generation of connected devices. We have also seen that wolfSSL is popular for device developers implementing code signing.
If you want to test wolfSSL for ThreadX, just download our latest source and build it in your environment. Let us know if you face any issues and we’ll be happy to help. Just email us at info@yassl.com!
wolfSSL’s OpenSSL Compatibility
Hi!
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 Stunnel. Contact us if you would like help compiling wolfSSL with Lighttpd or stunnel. We’ll be happy to help!
The wolfSSL embedded SSL Library is integrated into LuCI
Did you know that wolfSSL is integrated into the LuCI project, which is a web interface for embedded devices? LuCI is an interface tool for wireless routers. See here for project details: http://luci.subsignal.org/
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: http://www.ietf.org/rfc/rfc5246.txt. 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.
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: http://www.sdtimes.com/blog/post/2010/03/04/The-state-of-software-security.aspx.
Get the report from Veracode here: https://www.veracode.com/sites/default/files/Resources/Reports/state-of-software-security-volume-2-executive-summary-report.pdf. Registration is not required to download the report. The detailed report is an excellent document.
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 info@yassl.com to receive the beta.
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!
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 info@yassl.com to receive the beta.
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.”
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.
yaSSL Release 1.9.8
The yaSSL SSL library Release 1.9.8 is now available for download.
Release 1.9.8 for yaSSL adds bug fixes and support for the new stream ciphers Rabbit and HC-128. We expect that these new stream ciphers will be especially useful to users that are encrypting streaming media like voice (VoIP) or video.
wolfSSL Release 1.1.0
The wolfSSL embedded SSL library Release 1.1.0 is now available for download.
Release 1.1.0 for wolfSSL adds bug fixes, a check against malicious session cache use, support for lighttpd, and TLS 1.2.
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 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.
CyaSSL Embedded SSL Release 1.0.3
The CyaSSL embedded SSL library Release 1.0.3 is now available for download. Release 1.0.3 for CyaSSL adds bug fixes and improves OpenSSL compatibility support. We believe that the CyaSSL now supports the bulk of the functions required to port applications over from OpenSSL.
Release 1.0.3 includes an alpha release of DTLS (http://en.wikipedia.org/wiki/Datagram_Transport_Layer_Security) for both clients and servers. This is only for testing purposes at this time. Rebroadcast and reordering aren’t fully implemented at this time but will be for the next release.
Weekly updates
Archives
- December 2024 (5)
- 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)