generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

RT1744: SSL_CTX_set_dump_dh() doc feedback

Browse Source 
The description of when the server creates a DH key is
confusing.  This cleans it up.
(rsalz: also removed trailing whitespace.)

Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
This commit is contained in:
David Gatwood 2014-08-26 13:02:03 -04:00 committed by Rich Salz
parent 27b0494153
commit b88ffa2bce
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/ssl/SSL_CTX_set_tmp_dh_callback.pod
View File

@ -48,12 +48,13 @@ even if he gets hold of the normal (certified) key, as this key was
only used for signing. only used for signing.
In order to perform a DH key exchange the server must use a DH group In order to perform a DH key exchange the server must use a DH group
(DH parameters) and generate a DH key. The server will always generate a new (DH parameters) and generate a DH key.
DH key during the negotiation, when the DH parameters are supplied via The server will always generate a new DH key during the negotiation
callback and/or when the SSL_OP_SINGLE_DH_USE option of if either the DH parameters are supplied via callback or the
L<SSL_CTX_set_options(3)|SSL_CTX_set_options(3)> is set. It will SSL_OP_SINGLE_DH_USE option of SSL_CTX_set_options(3) is set (or both).
immediately create a DH key, when DH parameters are supplied via It will immediately create a DH key if DH parameters are supplied via
SSL_CTX_set_tmp_dh() and SSL_OP_SINGLE_DH_USE is not set. In this case, SSL_CTX_set_tmp_dh() and SSL_OP_SINGLE_DH_USE is not set.
In this case,
it may happen that a key is generated on initialization without later it may happen that a key is generated on initialization without later
being needed, while on the other hand the computer time during the being needed, while on the other hand the computer time during the
negotiation is being saved. negotiation is being saved.