Commit 5497c13
doc: update outdated section on TLSv1.3-PSK
Recent OpenSSL versions support PSKs with non-SHA-256 TLSv1.3 ciphers,
e.g., TLS_AES_256_GCM_SHA384.
PR-URL: #48123
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent 281dfaf commit 5497c13
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -173,8 +173,8 @@ low-entropy sources is not secure. | |||
| 173 | 173 | PSK ciphers are disabled by default, and using TLS-PSK thus requires explicitly | |
| 174 | 174 | specifying a cipher suite with the `ciphers` option. The list of available | |
| 175 | 175 | ciphers can be retrieved via `openssl ciphers -v 'PSK'`. All TLS 1.3 | |
| 176 | - ciphers are eligible for PSK but currently only those that use SHA256 digest are | ||
| 177 | - supported they can be retrieved via `openssl ciphers -v -s -tls1_3 -psk`. | ||
| 176 | + ciphers are eligible for PSK and can be retrieved via | ||
| 177 | + `openssl ciphers -v -s -tls1_3 -psk`. | ||
| 178 | 178 | ||
| 179 | 179 | According to the [RFC 4279][], PSK identities up to 128 bytes in length and | |
| 180 | 180 | PSKs up to 64 bytes in length must be supported. As of OpenSSL 1.1.0 | |
0 commit comments