wolfSSL (formerly CyaSSL) is a small, fast, portable implementation of TLS/SSL for embedded devices to the cloud. wolfSSL supports up to TLS 1.3!
 
 
 
 
 
 
Go to file
Sean Parkinson 20950ffde8 Remove TODOs around TLS 1.3 draft version. 2018-08-21 08:41:50 +10:00
IDE Enhancements to the GCC-ARM example to support FIPS and additional build options. Added examples for memory overrides and standard library overrides. Fixes for building without test, benchmark or TLS. Changed the ARM startup code to only work for the Cortex M0 example using the define `USE_WOLF_ARM_STARTUP`. 2018-08-13 12:22:14 -06:00
IPP
certs Support for more cert subject OIDs and raw subject access (#1734) 2018-08-12 12:53:29 -07:00
ctaocrypt
cyassl Fix TCP with Timeout 2018-05-23 11:29:16 -07:00
doc Support for more cert subject OIDs and raw subject access (#1734) 2018-08-12 12:53:29 -07:00
examples account for NO_RSA and SP math when printing max RSA key size 2018-08-15 09:52:43 -06:00
lib
m4 Configure Update 2018-07-03 14:42:51 -07:00
mcapi Fixes for build failures. Added new `WC_MAX_SYM_KEY_SIZE` macro for helping determine max key size. Added enum for unique cipher types. Added `CHACHA_MAX_KEY_SZ` for ChaCha. 2018-04-09 13:28:15 -07:00
mplabx
mqx
rpm RPM Fixes 2018-06-22 11:55:09 -07:00
scripts key size check on ocsp-stapling2 test 2018-08-15 09:52:43 -06:00
src Remove TODOs around TLS 1.3 draft version. 2018-08-21 08:41:50 +10:00
sslSniffer
support
swig
tests Merge pull request #1758 from dgarske/certext 2018-08-14 17:00:51 -05:00
testsuite
tirtos
wolfcrypt silence warning for unreachable statement from some compilers. 2018-08-17 15:13:06 -06:00
wolfssl Use final TLS 1.3 version value by default. 2018-08-20 14:17:38 +10:00
wrapper update IO callback function names with CSharp wrapper 2018-06-20 09:10:19 -06:00
.cproject
.gitignore Added new build option `--enable-memtest` or `WOLFSSL_FORCE_MALLOC_FAIL_TEST` which enables random malloc failures for testing. This test supresses the `abort()` calls to detect seg faults. A new script `./scripts/memtest.sh` starts the test. If an issue is found it can be reviewed with the `./scripts/memtest.txt` log and reproduced using the seed printed at top of unit test as `--- RNG MALLOC FAIL AT 295---` and rerun using `./tests/unit.test 295`. 2018-07-30 13:53:35 -07:00
.project
AUTHORS
COPYING
ChangeLog.md prepare for release v3.15.3 2018-06-21 12:22:27 -06:00
INSTALL
LICENSING
Makefile.am prepare for release v3.15.3 2018-06-21 12:22:27 -06:00
README prepare for release v3.15.3 2018-06-21 12:22:27 -06:00
README.md prepare for release v3.15.3 2018-06-21 12:22:27 -06:00
SCRIPTS-LIST Added new `async-check.sh` script for setting up the async simulator for internal testing. 2018-05-11 16:38:24 +02:00
Vagrantfile
async-check.sh Added new `async-check.sh` script for setting up the async simulator for internal testing. 2018-05-11 16:38:24 +02:00
autogen.sh Test Fixes 2018-05-16 15:47:12 -04:00
commit-tests.sh
configure.ac Use final TLS 1.3 version value by default. 2018-08-20 14:17:38 +10:00
fips-check.sh FIPS build and ECC fixes 2018-07-19 10:02:14 -07:00
gencertbuf.pl Benchmark support for 3072-bit RSA and DH when `USE_CERT_BUFFERS_3072` is defined. 2018-06-22 09:30:33 -07:00
input
pre-commit.sh
pre-push.sh
pull_to_vagrant.sh
quit
stamp-h.in
valgrind-error.sh
wnr-example.conf
wolfssl-ntru.sln
wolfssl-ntru.vcproj
wolfssl.sln
wolfssl.vcproj
wolfssl.vcxproj
wolfssl64.sln

README.md

Description

The wolfSSL embedded SSL library (formerly CyaSSL) is a lightweight SSL/TLS library written in ANSI C and targeted for embedded, RTOS, and resource-constrained environments - primarily because of its small size, speed, and feature set. It is commonly used in standard operating environments as well because of its royalty-free pricing and excellent cross platform support. wolfSSL supports industry standards up to the current TLS 1.3 and DTLS 1.3 levels, is up to 20 times smaller than OpenSSL, and offers progressive ciphers such as ChaCha20, Curve25519, NTRU, and Blake2b. User benchmarking and feedback reports dramatically better performance when using wolfSSL over OpenSSL.

wolfSSL is powered by the wolfCrypt library. A version of the wolfCrypt cryptography library has been FIPS 140-2 validated (Certificate #2425). For additional information, visit the wolfCrypt FIPS FAQ or contact fips@wolfssl.com

Why Choose wolfSSL?

There are many reasons to choose wolfSSL as your embedded SSL solution. Some of the top reasons include size (typical footprint sizes range from 20-100 kB), support for the newest standards (SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2, TLS 1.3, DTLS 1.0, and DTLS 1.2), current and progressive cipher support (including stream ciphers), multi-platform, royalty free, and an OpenSSL compatibility API to ease porting into existing applications which have previously used the OpenSSL package. For a complete feature list, see Section 4.1.


Notes - Please read

Note 1

wolfSSL as of 3.6.6 no longer enables SSLv3 by default.  wolfSSL also no
longer supports static key cipher suites with PSK, RSA, or ECDH.  This means
if you plan to use TLS cipher suites you must enable DH (DH is on by default),
or enable ECC (ECC is on by default), or you must enable static
key cipher suites with
    WOLFSSL_STATIC_DH
    WOLFSSL_STATIC_RSA
    or
    WOLFSSL_STATIC_PSK

though static key cipher suites are deprecated and will be removed from future
versions of TLS.  They also lower your security by removing PFS.  Since current
NTRU suites available do not use ephemeral keys, WOLFSSL_STATIC_RSA needs to be
used in order to build with NTRU suites.


When compiling ssl.c, wolfSSL will now issue a compiler error if no cipher suites
are available.  You can remove this error by defining WOLFSSL_ALLOW_NO_SUITES
in the event that you desire that, i.e., you're not using TLS cipher suites.

Note 2


wolfSSL takes a different approach to certificate verification than OpenSSL
does.  The default policy for the client is to verify the server, this means
that if you don't load CAs to verify the server you'll get a connect error,
no signer error to confirm failure (-188).  If you want to mimic OpenSSL
behavior of having SSL_connect succeed even if verifying the server fails and
reducing security you can do this by calling:

wolfSSL_CTX_set_verify(ctx, SSL_VERIFY_NONE, 0);

before calling wolfSSL_new();  Though it's not recommended.

Note 3

The enum values SHA, SHA256, SHA384, SHA512 are no longer available when
wolfSSL is built with --enable-opensslextra (OPENSSL_EXTRA) or with the macro
NO_OLD_SHA_NAMES. These names get mapped to the OpenSSL API for a single call
hash function. Instead the name WC_SHA, WC_SHA256, WC_SHA384 and WC_SHA512
should be used for the enum name.

wolfSSL Release 3.15.3 (6/20/2018)

Release 3.15.3 of wolfSSL embedded TLS has bug fixes and new features including:

  • ECDSA blinding added for hardening against side channel attacks
  • Fix for compatibility layer build with no server and no client defined
  • Use of optimized Intel assembly instructions on compatible AMD processor
  • wolfCrypt Nucleus port additions
  • Fix added for MatchDomainName and additional tests added
  • Fixes for building with WOLFSSL_ATECC508A defined
  • Fix for verifying a PKCS7 file in BER format with indefinite size

This release of wolfSSL fixes 2 security vulnerability fixes.

Medium level fix for PRIME + PROBE attack combined with a variant of Lucky 13. Constant time hardening was done to avoid potential cache-based side channel attacks when verifying the MAC on a TLS packet. CBC cipher suites are susceptible on systems where an attacker could gain access and run a parallel program for inspecting caching. Only wolfSSL users that are using TLS/DTLS CBC cipher suites need to update. Users that have only AEAD and stream cipher suites set, or have built with WOLFSSL_MAX_STRENGTH (--enable-maxstrength), are not vulnerable. Thanks to Eyal Ronen, Kenny Paterson, and Adi Shamir for the report.

Medium level fix for a ECDSA side channel attack. wolfSSL is one of over a dozen vendors mentioned in the recent Technical Advisory “ROHNP” by author Ryan Keegan. Only wolfSSL users with long term ECDSA private keys using our fastmath or normal math libraries on systems where attackers can get access to the machine using the ECDSA key need to update. An attacker gaining access to the system could mount a memory cache side channel attack that could recover the key within a few thousand signatures. wolfSSL users that are not using ECDSA private keys, that are using the single precision math library, or that are using ECDSA offloading do not need to update. (blog with more information https://www.wolfssl.com/wolfssh-and-rohnp/)

See INSTALL file for build instructions. More info can be found on-line at http://wolfssl.com/wolfSSL/Docs.html

Resources

wolfSSL Website

wolfSSL Wiki

FIPS FAQ

wolfSSL Manual

wolfSSL API Reference

wolfCrypt API Reference

TLS 1.3