WolfSSL
Template:Lowercasetitle Template:Infobox software 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.[1]
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, macOS, 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.[2] yaSSL, alternatively, was developed and dual-licensed under both a commercial license and the GPL.[3] yaSSL offered a more modern API, commercial style developer support and was complete with an OpenSSL compatibility layer.[1] The first major user of wolfSSL/CyaSSL/yaSSL was MySQL.[4] Through bundling with MySQL, yaSSL has achieved extremely high distribution volumes in the millions.
Protocols
- Main article: Transport Layer Security
The wolfSSL lightweight SSL library implements the following protocols:[5]
- SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2
- DTLS 1.0, DTLS 1.2
Protocol Notes:
- SSL 2.0 - SSL 2.0 was deprecated (prohibited) in 2011 by RFC 6176. wolfSSL does not support it.
- SSL 3.0 - SSL 3.0 was deprecated (prohibited) in 2015 by RFC 7568. In response to the POODLE attack, SSL 3.0 has been disabled by default since wolfSSL 3.6.6, but can be enabled with a compile-time option.[6]
Algorithms
wolfSSL uses the following cryptography libraries:
wolfCrypt
By default, wolfSSL uses the cryptographic services provided by wolfCrypt.[7] 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[8] (where it can be enabled using a build option).
NTRU
CyaSSL+ includes NTRU[9] public key encryption. The addition of NTRU in CyaSSL+ was a result of the partnership between yaSSL and Security Innovation.[9] 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[10]Template:Better source). 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.
Hardware Acceleration Platforms Supported
- Intel AES-NI (Xeon and Core processor families)
| AES-GCM | 128, 192, 256 bit | |
| AES-CCM | 128, 192, 256 bit | |
| AES-CBC | 128, 192, 256 bit | |
| AES-ECB | 128, 192, 256 bit | |
| AES-CTR | 128, 192, 256 bit |
- AVX1/AVX2 (Intel and AMD x86)
| SHA-256 | |
| SHA-384 | |
| SHA-512 |
- RDRAND (Intel 64, IA-32 architectures)
| SHA-256 | |
| SHA-512 |
- RDSEED (Intel Broadwell, AMD Zen)
| SHA-256 | |
| SHA-512 |
- Freescale Coldfire SEC (NXP MCF547X and MCF548X)
| DES-CBC | 64 bit | |
| 3DES-CBC | 192 bit | |
| AES-CBC | 128, 192, 256 bit |
- Freescale Kinetis MMCAU K50, K60, K70 and K80 (ARM Cortex-M4 core)
| MD5 | 128 bit digest | |
| SHA1 | 160 bit digest | |
| SHA256 | ||
| DES-CBC | 64 bit | |
| 3DES-CBC | 192 bit | |
| AES-CBC | 128, 192, 256 bit | |
| AES-CCM | 128, 192, 256 bit | |
| AES-GCM | 128, 192, 256 bit | |
| AES-ECB | 128, 192, 256 bit |
- STMicroelectronics STM32 F1, F2, F4, L1, W Series (ARM Cortex - M3/M4)
| RNG | ||
| DES-CBC | 64 bit | |
| DES-ECB | 64 bit Encrypt | |
| 3DES-CBC | 192 bit | |
| MD5 | 128 bit | |
| SHA1 | 160 bit | |
| AES-CBC | 128, 192, 256 bit | |
| AES-CTR | 128, 192, 256 bit |
- CubeMX and Std Per Lib
- Cavium NITROX (III/V PX processors)
| RNG | ||
| AES-CBC | 128, 192, 256 bit | |
| 3DES-CBC | 192 bit | |
| RC4 | 2048 bit maximum | |
| HMAC | MD5, SHA1, SHA256 | |
| RSA | 512 - 4096 bit |
- Microchip PIC32 MX/MZ (Embedded Connectivity)
| MD5 | 128 bit digest | |
| SHA1 | 160 bit digest | |
| SHA256 | ||
| HMAC | MD5, SHA1, SHA256 | |
| DES-CBC | 64 bit | |
| 3DES-CBC | 192 bit | |
| AES-CBC | 128, 192, 256 bit | |
| AES-CTR | 128, 192, 256 bit | |
| AES-GCM | 128, 192, 256 bit |
- Texas Instruments TM4C1294 (ARM Cortex-M4F)
| DES-CBC | 64 bit | |
| 3DES-CBC | 192 bit | |
| AES-CCM | 128, 192, 256 bit | |
| AES-GCM | 128, 192, 256 bit | |
| AES-ECB | 128, 192, 256 bit | |
| AES-CTR | 128, 192, 256 bit | |
| AES-CBC | 128, 192, 256 bit |
- Nordic NRF51 (Series SoC family, 32-bit ARM Cortex M0 processor core)
| AES-ECB | 128 bit | |
| RNG |
| ECC | 256 bit (NIST-P256) |
| AES-CBC | 128, 192, 256 bit | |
| AES-CTR | 128, 192, 256 bit | |
| AES-GCM | 128, 192, 256 bit | |
| SHA256 |
- Intel QuickAssist Technology (Contact if interested)
| RSA | 512 - 4096 bit | |
| SHA1 | 160 bit digest | |
| SHA2 | 224, 256, 384 and 512 bit | |
| AES-CBC | 128, 192, 256 bit | |
| AES-GCM | 128, 192, 256 bit | |
| ECC | 128, 256 bit | |
| HMAC | SHA1, SHA2 | |
| MD5 |
- Freescale NXP LTC
| Curve25519 | 256 bit | |
| Ed25519 | 256 bit | |
| AES-CCM | 128, 192, 256 bit | |
| AES-ECB | 128, 192, 256 bit | |
| AES-CBC | 128, 192, 256 bit | |
| AES-CTR | 128, 192, 256 bit | |
| AES-GCM | 128, 192, 256 bit | |
| SHA1 | 160 bit digest | |
| SHA256 | ||
| ECC | 128, 256 bit | |
| ECC-DHE | 128, 256 bit | |
| RSA | 512 - 4096 bit |
Licensing
wolfSSL is Open Source, licensed under the GNU General Public License GPLv2.[11]
Awards
2011 Tomorrow's Technology Today - Mobile Encryption[12]
2015 Cybersecurity 500 - wolfSSL[13]
2016 Cybersecurity 500 - wolfSSL[14]
2017 Cybersecurity 500 - wolfSSL[15]
See also
- Transport Layer Security
- Comparison of TLS implementations
- Comparison of cryptography libraries
- GnuTLS
- Network Security Services
- OpenSSL
References
External links
Template:Cryptographic software Template:SSL/TLS
- ↑ 1.0 1.1 wolfSSL - Embedded Communications Products
- ↑ OpenSSL: Source, License
- ↑ wolfSSL - License
- ↑ MySQL, Building MySQL with Support for Secure Connections
- ↑ wolfSSL - Docs | CyaSSL Manual - Chapter 4 (Features)
- ↑ "wolfSSL 3.6.6 is Now Available".
- ↑ wolfSSL - Docs | wolfSSL Manual - Chapter 10 (wolfCrypt Usage Reference)
- ↑ Kerberos: The Network Authentication Protocol
- ↑ 9.0 9.1 NTRU CryptoLabs
- ↑ Intel SGX
- ↑ GNU License
- ↑ 2011 Tomorrow's Technology Today - Mobile Encryption
- ↑ Cybersecurity Ventures - Cybersecurity 500
- ↑ Cybersecurity Ventures - Cybersecurity 500
- ↑ [1]