-
-
Notifications
You must be signed in to change notification settings - Fork 494
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tls: remove support for TLS 1.0 and 1.1.
Those old algorithms are not used anywhere, and are not recommended. TLS 1.2 support has been prevalent for over a decade.
- Loading branch information
Showing
6 changed files
with
18 additions
and
65 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
= nng_tls_config_version(3tls) | ||
// | ||
// Copyright 2020 Staysail Systems, Inc. <[email protected]> | ||
// Copyright 2024 Staysail Systems, Inc. <[email protected]> | ||
// | ||
// This document is supplied under the terms of the MIT License, a | ||
// copy of which should be located in the distribution where this | ||
|
@@ -20,8 +20,6 @@ nng_tls_config_version - configure TLS version | |
#include <nng/supplemental/tls/tls.h> | ||
typedef enum nng_tls_version { | ||
NNG_TLS_1_0 = 0x301, | ||
NNG_TLS_1_1 = 0x302, | ||
NNG_TLS_1_2 = 0x303, | ||
NNG_TLS_1_3 = 0x304 | ||
} nng_tls_version; | ||
|
@@ -41,29 +39,17 @@ By default (if this function is not called), NNG will attempt to use both TLS v1 | |
|
||
Clients and servers will generally negotiate for the highest mutually supported TLS version. | ||
|
||
TIP: As of this writing, we recommend setting the minimum to | ||
`NNG_TLS_1_2` (TLS v1.2) and the maximum to `NNG_TLS_1_3` (TLS v1.3). | ||
This gives the best security, while ensuring good interoperability. | ||
Nearly all modern TLS implementations support TLS v1.2. | ||
|
||
TIP: Support for TLS v1.3 is available via external TLS engines. | ||
|
||
NOTE: The cipher-suites supported by TLS v1.3 are different from earlier versions. | ||
Therefore it may be necessary to generate different certificates. | ||
|
||
== CAVEATS | ||
|
||
* SSL v2.0 and v3.0 are insecure, and not supported in NNG. | ||
|
||
* TLS v1.3 is not supported by the default _Mbed TLS_ engine at this time. | ||
* SSL v2.0, SSL v3.0, TLS v1.0 and TLS v1.1 are insecure, and not supported in NNG. | ||
|
||
* Some TLS engines may not support limiting the maximum version. | ||
|
||
* TLS v1.3 Zero Round Trip Time (0-RTT) is not supported in NNG. | ||
|
||
* Session resumption is not supported in NNG (for any TLS version). | ||
|
||
* TLS PSK support is not supported in NNG. (This is a limitation planned to be addressed.) | ||
* TLS PSK support is dependent upon the engine. | ||
|
||
== RETURN VALUES | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters