wolfSSL

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Alex Abrahamson (talk | contribs) at 23:23, 17 September 2018 (Updated list of supported platforms). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

wolfSSL
Developer(s)Todd Ouska
Initial releaseFebruary 19, 2006 (2006-02-19)[1]
Stable release5.6.4 (October 30, 2023; 6 months ago (2023-10-30)[2]) [±]
Repository
Written inC language
Operating systemMulti-platform
TypeSecurity library
LicenseGNU General Public License or Commercial Distribution License
Websitewww.wolfssl.com

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, 1.3, 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 APIs, 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, 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, uT-kernel, embOS, INtime, mbed, RIOT, CMSIS-RTOS, FROSTED, Green Hills INTEGRITY, Keil RTX, TOPPERS, PetaLinux, and Apache Mynewt.

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]

  • SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2, TLS 1.3
  • 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.[8]

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, SHA-3, 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][better source needed]). 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
ChaCha20
Poly1305
RDRAND (Intel 64, IA-32 architectures)
RDSEED (Intel Broadwell, AMD Zen)
Freescale Cryptographic Accelerator and Assurance Module (CAAM)
AES
Hashing
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, SHA3
RSA 512 - 4096 bit
ECC NIST Prime 192, 224, 256, 384 and 521
Cavium NITROX V
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
Microchip/Atmel ATECC508A (compatible with any MPU or MCU including: Atmel SMART and AVR MCUs)
ECC 256 bit (NIST-P256)
ARMv8
AES-CBC 128, 192, 256 bit
AES-CTR 128, 192, 256 bit
AES-GCM 128, 192, 256 bit
SHA256
Intel QuickAssist Technology
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.[13]

See also

References

  1. ^ "wolfSSL ChangeLog".
  2. ^ "wolfSSL ChangeLog". 2023-10-31. Retrieved 2023-10-31.
  3. ^ a b wolfSSL - Embedded Communications Products
  4. ^ OpenSSL: Source, License
  5. ^ wolfSSL - License
  6. ^ MySQL, Building MySQL with Support for Secure Connections
  7. ^ wolfSSL - Docs | CyaSSL Manual - Chapter 4 (Features)
  8. ^ "wolfSSL 3.6.6 is Now Available".
  9. ^ wolfSSL - Docs | wolfSSL Manual - Chapter 10 (wolfCrypt Usage Reference)
  10. ^ Kerberos: The Network Authentication Protocol
  11. ^ a b NTRU CryptoLabs Archived 2013-02-02 at archive.today
  12. ^ Intel SGX
  13. ^ GNU License

External links