source: azure_iot_hub_f767zi/trunk/wolfssl-4.7.0/README@ 464

Last change on this file since 464 was 464, checked in by coas-nagasima, 3 years ago

WolfSSLとAzure IoT SDKを更新

File size: 8.3 KB
Line 
1*** Description ***
2
3The wolfSSL embedded SSL library (formerly CyaSSL) is a lightweight SSL/TLS
4library written in ANSI C and targeted for embedded, RTOS, and
5resource-constrained environments - primarily because of its small size, speed,
6and feature set. It is commonly used in standard operating environments as well
7because of its royalty-free pricing and excellent cross platform support.
8wolfSSL supports industry standards up to the current TLS 1.3 and DTLS 1.2
9levels, is up to 20 times smaller than OpenSSL, and offers progressive ciphers
10such as ChaCha20, Curve25519, NTRU, and Blake2b. User benchmarking and feedback
11reports dramatically better performance when using wolfSSL over OpenSSL.
12
13wolfSSL is powered by the wolfCrypt library. Two versions of the wolfCrypt
14cryptography library have been FIPS 140-2 validated (Certificate #2425 and
15certificate #3389). For additional information, visit the wolfCrypt FIPS FAQ
16(https://www.wolfssl.com/license/fips/) or contact fips@wolfssl.com
17
18*** Why choose wolfSSL? ***
19
20There are many reasons to choose wolfSSL as your embedded SSL solution. Some of
21the top reasons include size (typical footprint sizes range from 20-100 kB),
22support for the newest standards (SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2, TLS 1.3,
23DTLS 1.0, and DTLS 1.2), current and progressive cipher support (including
24stream ciphers), multi-platform, royalty free, and an OpenSSL compatibility API
25to ease porting into existing applications which have previously used the
26OpenSSL package. For a complete feature list, see chapter 4 of the wolfSSL
27manual. (https://www.wolfssl.com/docs/wolfssl-manual/ch4/)
28
29*** Notes, Please read ***
30
31Note 1)
32wolfSSL as of 3.6.6 no longer enables SSLv3 by default. wolfSSL also no longer
33supports static key cipher suites with PSK, RSA, or ECDH. This means if you
34plan to use TLS cipher suites you must enable DH (DH is on by default), or
35enable ECC (ECC is on by default), or you must enable static key cipher suites
36with
37
38 WOLFSSL_STATIC_DH
39 WOLFSSL_STATIC_RSA
40 or
41 WOLFSSL_STATIC_PSK
42
43though static key cipher suites are deprecated and will be removed from future
44versions of TLS. They also lower your security by removing PFS. Since current
45NTRU suites available do not use ephemeral keys, WOLFSSL_STATIC_RSA needs to be
46used in order to build with NTRU suites.
47
48When compiling ssl.c, wolfSSL will now issue a compiler error if no cipher
49suites are available. You can remove this error by defining
50WOLFSSL_ALLOW_NO_SUITES in the event that you desire that, i.e., you're not
51using TLS cipher suites.
52
53Note 2)
54wolfSSL takes a different approach to certificate verification than OpenSSL
55does. The default policy for the client is to verify the server, this means
56that if you don't load CAs to verify the server you'll get a connect error,
57no signer error to confirm failure (-188).
58
59If you want to mimic OpenSSL behavior of having SSL_connect succeed even if
60verifying the server fails and reducing security you can do this by calling:
61
62 wolfSSL_CTX_set_verify(ctx, SSL_VERIFY_NONE, 0);
63
64before calling wolfSSL_new();. Though it's not recommended.
65
66Note 3)
67The enum values SHA, SHA256, SHA384, SHA512 are no longer available when
68wolfSSL is built with --enable-opensslextra (OPENSSL_EXTRA) or with the macro
69NO_OLD_SHA_NAMES. These names get mapped to the OpenSSL API for a single call
70hash function. Instead the name WC_SHA, WC_SHA256, WC_SHA384 and WC_SHA512
71should be used for the enum name.
72
73*** end Notes ***
74
75
76# wolfSSL Release 4.7.0 (February 16, 2021)
77Release 4.7.0 of wolfSSL embedded TLS has bug fixes and new features including:
78
79### New Feature Additions
80* Compatibility Layer expansion SSL_get_verify_mode, X509_VERIFY_PARAM API, X509_STORE_CTX API added
81* WOLFSSL_PSK_IDENTITY_ALERT macro added for enabling a subset of TLS alerts
82* Function wolfSSL_CTX_NoTicketTLSv12 added to enable turning off session tickets with TLS 1.2 while keeping TLS 1.3 session tickets available
83* Implement RFC 5705: Keying Material Exporters for TLS
84* Added --enable-reproducible-build flag for making more deterministic library outputs to assist debugging
85
86### Fixes
87* Fix to free mutex when cert manager is free’d
88* Compatibility layer EVP function to return the correct block size and type
89* DTLS secure renegotiation fixes including resetting timeout and retransmit on duplicate HelloRequest
90* Fix for edge case with shrink buffer and secure renegotiation
91* Compile fix for type used with curve448 and PPC64
92* Fixes for SP math all with PPC64 and other embedded compilers
93* SP math all fix when performing montgomery reduction on one word modulus
94* Fixes to SP math all to better support digit size of 8-bit
95* Fix for results of edge case with SP integer square operation
96* Stop non-ct mod inv from using register x29 with SP ARM64 build
97* Fix edge case when generating z value of ECC with SP code
98* Fixes for PKCS7 with crypto callback (devId) with RSA and RNG
99* Fix for compiling builds with RSA verify and public only
100* Fix for PKCS11 not properly exporting the public key due to a missing key type field
101* Call certificate callback with certificate depth issues
102* Fix for out-of-bounds read in TLSX_CSR_Parse()
103* Fix incorrect AES-GCM tag generation in the EVP layer
104* Fix for out of bounds write with SP math all enabled and an edge case of calling sp_tohex on the result of sp_mont_norm
105* Fix for parameter check in sp_rand_prime to handle 0 length values
106* Fix for edge case of failing malloc resulting in an out of bounds write with SHA256/SHA512 when small stack is enabled
107
108
109### Improvements/Optimizations
110* Added --enable-wolftpm option for easily building wolfSSL to be used with wolfTPM
111* DTLS macro WOLFSSL_DTLS_RESEND_ONLY_TIMEOUT added for resending flight only after a timeout
112* Update linux kernel module to use kvmalloc and kvfree
113* Add user settings option to cmake build
114* Added support for AES GCM session ticket encryption
115* Thread protection for global RNG used by wolfSSL_RAND_bytes function calls
116* Sanity check on FIPs configure flag used against the version of FIPs bundle
117* --enable-aesgcm=table now is compatible with --enable-linuxkm
118* Increase output buffer size that wolfSSL_RAND_bytes can handle
119* Out of directory builds resolved, wolfSSL can now be built in a separate directory than the root wolfssl directory
120
121### Vulnerabilities
122* [HIGH] CVE-2021-3336: In earlier versions of wolfSSL there exists a potential man in the middle attack on TLS 1.3 clients. Malicious attackers with a privileged network position can impersonate TLS 1.3 servers and bypass authentication. Users that have applications with client side code and have TLS 1.3 turned on, should update to the latest version of wolfSSL. Users that do not have TLS 1.3 turned on, or that are server side only, are NOT affected by this report. For the code change see https://github.com/wolfSSL/wolfssl/pull/3676.
123* [LOW] In the case of using custom ECC curves there is the potential for a crafted compressed ECC key that has a custom prime value to cause a hang when imported. This only affects applications that are loading in ECC keys with wolfSSL builds that have compressed ECC keys and custom ECC curves enabled.
124* [LOW] With TLS 1.3 authenticated-only ciphers a section of the server hello could contain 16 bytes of uninitialized data when sent to the connected peer. This affects only a specific build of wolfSSL with TLS 1.3 early data enabled and using authenticated-only ciphers with TLS 1.3.
125
126
127For additional vulnerability information visit the vulnerability page at
128https://www.wolfssl.com/docs/security-vulnerabilities/
129
130See INSTALL file for build instructions.
131More info can be found on-line at https://wolfssl.com/wolfSSL/Docs.html
132
133
134
135*** Resources ***
136
137
138[wolfSSL Website](https://www.wolfssl.com/)
139
140[wolfSSL Wiki](https://github.com/wolfSSL/wolfssl/wiki)
141
142[FIPS FAQ](https://wolfssl.com/license/fips)
143
144[wolfSSL Documents](https://wolfssl.com/wolfSSL/Docs.html)
145
146[wolfSSL Manual](https://wolfssl.com/wolfSSL/Docs-wolfssl-manual-toc.html)
147
148[wolfSSL API Reference]
149(https://wolfssl.com/wolfSSL/Docs-wolfssl-manual-17-wolfssl-api-reference.html)
150
151[wolfCrypt API Reference]
152(https://wolfssl.com/wolfSSL/Docs-wolfssl-manual-18-wolfcrypt-api-reference.html)
153
154[TLS 1.3](https://www.wolfssl.com/docs/tls13/)
155
156[wolfSSL Vulnerabilities]
157(https://www.wolfssl.com/docs/security-vulnerabilities/)
Note: See TracBrowser for help on using the repository browser.