wolfSSL

wolfSSL
Developer(s) Todd Ouska
Initial release February 19, 2006 (2006-02-19)[1]
Stable release 3.9.10 (September 23, 2016 (2016-09-23)[2]) [±]
Development status Active
Written in C language
Operating system Multi-platform
Type Security library
License GNU General Public License or Commercial Distribution License
Website www.wolfssl.com/wolfSSL/Home.html

wolfSSL (formerly CyaSSL or yet another SSL) is a small, portable, embedded SSL/TLS library targeted for use by embedded systems developers. It is an open source implementation of TLS (SSL 3.0, TLS 1.0, 1.1, 1.2, and DTLS 1.0 and 1.2) written in the C language. It includes SSL/TLS client libraries and an SSL/TLS server implementation as well as support for multiple API's, including those defined by SSL and TLS. wolfSSL also includes an OpenSSL compatibility interface with the most commonly used OpenSSL functions.[3]

A predecessor of wolfSSL, yaSSL is a C++ based SSL library for embedded environments and real time operating systems with constrained resources.

Platforms

wolfSSL is currently available for Win32/64, Linux, Mac OS X, Solaris, Threadx, VxWorks, FreeBSD, NetBSD, OpenBSD, embedded Linux, WinCE, Haiku, OpenWrt, iPhone, Android, Nintendo Wii and Gamecube through DevKitPro support, QNX, MontaVista, Tron variants, NonStop, OpenCL, Micrium's MicroC/OS-II, FreeRTOS, SafeRTOS, Freescale MQX, Nucleus, TinyOS, TI-RTOS, HP-UX, uTasker, and embOS.

History

The genesis of yaSSL, or yet another SSL, dates to 2004. OpenSSL was available at the time, and was dual licensed under the OpenSSL License and the SSLeay license.[4] yaSSL, alternatively, was developed and dual-licensed under both a commercial license and the GPL.[5] yaSSL offered a more modern API, commercial style developer support and was complete with an OpenSSL compatibility layer.[3] The first major user of wolfSSL/CyaSSL/yaSSL was MySQL.[6] Through bundling with MySQL, yaSSL has achieved extremely high distribution volumes in the millions.

Protocols

The wolfSSL lightweight SSL library implements the following protocols:[7]

Protocol Notes:

Algorithms

wolfSSL uses the following cryptography libraries:

wolfCrypt

By default, wolfSSL uses the cryptographic services provided by wolfCrypt.[9] wolfCrypt Provides RSA, ECC, DSS, Diffie–Hellman, EDH, NTRU, DES, Triple DES, AES (CBC, CTR, CCM, GCM), Camellia, IDEA, ARC4, HC-128, ChaCha20, MD2, MD4, MD5, SHA-1, SHA-2, BLAKE2, RIPEMD-160, Poly1305, Random Number Generation, Large Integer support, and base 16/64 encoding/decoding. An experimental cipher called Rabbit, a public domain software stream cipher from the EU's eSTREAM project, is also included. Rabbit is potentially useful to those encrypting streaming media in high performance, high demand environments.

wolfCrypt also includes support for the recent Curve25519 and Ed25519 algorithms.

wolfCrypt acts as a back-end crypto implementation for several popular software packages and libraries, including MIT Kerberos[10] (where it can be enabled using a build option).

NTRU

CyaSSL+ includes NTRU[11] public key encryption. The addition of NTRU in CyaSSL+ was a result of the partnership between yaSSL and Security Innovation.[11] NTRU works well in mobile and embedded environments due to the reduced bit size needed to provide the same security as other public key systems. In addition, it's not known to be vulnerable to quantum attacks. Several cipher suites utilizing NTRU are available with CyaSSL+ including AES-256, RC4, and HC-128.

SGX

wolfSSL supports use of Intel SGX (Software Guard Extensions[12]). Intel SGX allows for a smaller attack surface area and has been shown to provide a higher level of security for executing code without a significant negative impact on performance.

Licensing

wolfSSL is Open Source, licensed under the GNU General Public License GPLv2.[13]

Awards

2011 Tomorrow's Technology Today - Mobile Encryption[14]

2015 Cybersecurity 500 - wolfSSL[15]

2016 Cybersecurity 500 - wolfSSL[16]

See also

References

This article is issued from Wikipedia - version of the 10/11/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.