Skip to content

Commit 09c5e6a

Browse files
tniessendanielleadams
authored andcommitted
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 8907732 commit 09c5e6a

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
@@ -1880,12 +1880,13 @@ changes:
18801880
client certificate.
18811881
* `crl` {string|string\[]|Buffer|Buffer\[]} PEM formatted CRLs (Certificate
18821882
Revocation Lists).
1883-
* `dhparam` {string|Buffer} Diffie-Hellman parameters, required for
1883+
* `dhparam` {string|Buffer} Diffie-Hellman parameters, required for non-ECDHE
18841884
[perfect forward secrecy][]. Use `openssl dhparam` to create the parameters.
18851885
The key length must be greater than or equal to 1024 bits or else an error
18861886
will be thrown. Although 1024 bits is permissible, use 2048 bits or larger
18871887
for stronger security. If omitted or invalid, the parameters are silently
1888-
discarded and DHE ciphers will not be available.
1888+
discarded and DHE ciphers will not be available. [ECDHE][]-based [perfect
1889+
forward secrecy][] will still be available.
18891890
* `ecdhCurve` {string} A string describing a named curve or a colon separated
18901891
list of curve NIDs or names, for example `P-521:P-384:P-256`, to use for
18911892
ECDH key agreement. Set to `auto` to select the

0 commit comments

Comments
 (0)