You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| default_tls13 | X | X | X | X | X | X | X |||| X | X |
22
-
| default_fips ||| X || X | X |||| X | X ||
23
26
| 20190214 | X | X | X || X | X || X || X | X | X |
24
27
| 20170718 | X | X | X || X | X ||||| X | X |
25
28
| 20170405 | X | X | X || X | X || X ||| X | X |
@@ -43,13 +46,10 @@ The following chart maps the security policy version to protocol version and cip
43
46
The "default", "default_tls13", and "default_fips" versions are special in that they will be updated with future s2n-tls changes to keep up-to-date with current security best practices. Ciphersuites, protocol versions, and other options may be added or removed, or their internal order of preference might change. **Warning**: this means that the default policies may change as a result of library updates, which could break peers that rely on legacy options.
44
47
45
48
In contrast, numbered or dated versions are fixed and will never change. The numbered equivalents of the default policies are currently:
46
-
* "default": "20170210"
47
-
* "default_tls13": "20240417"
48
-
* "default_fips": "20240416"
49
-
50
-
"20230317" offers more limited but more secure options than the default policies. Consider it if you don't need or want to support less secure legacy options like TLS1.1 or SHA1. It is also FIPS compliant and supports TLS1.3. If you need a version of this policy that doesn't support TLS1.3, choose "20240331" instead.
51
-
52
-
"20160411" follows the same general preference order as "default". The main difference is it has a CBC cipher suite at the top. This is to accommodate certain Java clients that have poor GCM implementations. Users of s2n-tls who have found GCM to be hurting performance for their clients should consider this version.
49
+
* "default": "20240501"
50
+
* "default_fips": "20240502"
51
+
* "default_tls13": "20240503"
52
+
For previous defaults, see the "Default Policy History" section below.
53
53
54
54
"rfc9151" is derived from [Commercial National Security Algorithm (CNSA) Suite Profile for TLS and DTLS 1.2 and 1.3](https://datatracker.ietf.org/doc/html/rfc9151). This policy restricts the algorithms allowed for signatures on certificates in the certificate chain to RSA or ECDSA with sha384, which may require you to update your certificates.
55
55
Like the default policies, this policy may also change if the source RFC definition changes.
@@ -71,10 +71,13 @@ s2n-tls usually prefers AES over ChaCha20. However, some clients-- particularly
0 commit comments