nodejs · mildsunrise · mildsunrise · mildsunrise · Oct 20, 2020 · nodejs-github-bot
diff --git a/doc/api/tls.md b/doc/api/tls.md
@@ -146,6 +146,8 @@ 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`.
+On the client connection, a custom `checkServerIdentity` should be passed
+since the default one will fail in the absence of a certificate.
-since the default one will fail in the absence of a certificate.
+because the default one will fail in the absence of a certificate.
diff --git a/doc/api/tls.md b/doc/api/tls.md
@@ -154,6 +156,30 @@ maximum identity size is 128 bytes, and maximum PSK length is 256 bytes.
 The current implementation doesn't support asynchronous PSK callbacks due to the
 limitations of the underlying OpenSSL API.

+To use TLS-PSK, client and server should specify the `pskCallback` option,
diff --git a/doc/api/tls.md b/doc/api/tls.md
+* Returns: {Buffer|TypedArray|DataView} the PSK (or `null`).
+
+A return value of `null` stops the negotiation process and sends an
+"unknown_psk_identity" alert message to the other party.
-"unknown_psk_identity" alert message to the other party.
+`unknown_psk_identity` alert message to the other party.
	since the default one will fail in the absence of a certificate.
	because the default one will fail in the absence of a certificate.
	"unknown_psk_identity" alert message to the other party.
	`unknown_psk_identity` alert message to the other party.