Skip to content

Commit 00981ea

Browse files
authored
doc: fix description of TLS dhparam option
The dhparam option is not required for perfect forward secrecy in general. It is only required for non-ECDHE secrecy, but ECDHE-based secrecy is generally preferred anyway. PR-URL: #46949 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Filip Skokan <[email protected]>
1 parent 070e773 commit 00981ea

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

doc/api/tls.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -1882,12 +1882,13 @@ changes:
18821882
client certificate.
18831883
* `crl` {string|string\[]|Buffer|Buffer\[]} PEM formatted CRLs (Certificate
18841884
Revocation Lists).
1885-
* `dhparam` {string|Buffer} Diffie-Hellman parameters, required for
1885+
* `dhparam` {string|Buffer} Diffie-Hellman parameters, required for non-ECDHE
18861886
[perfect forward secrecy][]. Use `openssl dhparam` to create the parameters.
18871887
The key length must be greater than or equal to 1024 bits or else an error
18881888
will be thrown. Although 1024 bits is permissible, use 2048 bits or larger
18891889
for stronger security. If omitted or invalid, the parameters are silently
1890-
discarded and DHE ciphers will not be available.
1890+
discarded and DHE ciphers will not be available. [ECDHE][]-based [perfect
1891+
forward secrecy][] will still be available.
18911892
* `ecdhCurve` {string} A string describing a named curve or a colon separated
18921893
list of curve NIDs or names, for example `P-521:P-384:P-256`, to use for
18931894
ECDH key agreement. Set to `auto` to select the

0 commit comments

Comments
 (0)