From 0224e1412f1c550af811c381d520bcac228b2870 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tobias=20Nie=C3=9Fen?= Date: Thu, 25 May 2023 00:22:59 +0200 Subject: [PATCH] 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: https://github.com/nodejs/node/pull/48123 Reviewed-By: Rich Trott Reviewed-By: Luigi Pinca --- doc/api/tls.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/tls.md b/doc/api/tls.md index d8e3f9c27f4811..e1f0d28509ae34 100644 --- a/doc/api/tls.md +++ b/doc/api/tls.md @@ -173,8 +173,8 @@ low-entropy sources is not secure. PSK ciphers are disabled by default, and using TLS-PSK thus requires explicitly specifying a cipher suite with the `ciphers` option. The list of available ciphers can be retrieved via `openssl ciphers -v 'PSK'`. All TLS 1.3 -ciphers are eligible for PSK but currently only those that use SHA256 digest are -supported they can be retrieved via `openssl ciphers -v -s -tls1_3 -psk`. +ciphers are eligible for PSK and can be retrieved via +`openssl ciphers -v -s -tls1_3 -psk`. According to the [RFC 4279][], PSK identities up to 128 bytes in length and PSKs up to 64 bytes in length must be supported. As of OpenSSL 1.1.0