Lines Matching refs:parameters
51 (DH parameters) and generate a DH key. The server will always generate
54 As generating DH parameters is extremely time consuming, an application
55 should not generate the parameters on the fly. DH parameters can be reused, as
58 Typically applications should use well know DH parameters that have built-in
60 configure OpenSSL to use the default built-in DH parameters for the B<SSL_CTX>
65 If "auto" DH parameters are switched on then the parameters will be selected to
70 Applications may supply their own DH parameters instead of using the built-in
73 their own DH parameters should call SSL_CTX_set0_tmp_dh_pkey() or
74 SSL_set0_tmp_dh_pkey() to supply the parameters for the B<SSL_CTX> or B<SSL>
75 respectively. The parameters should be supplied in the I<dhpkey> argument as
76 an B<EVP_PKEY> containg DH parameters. Ownership of the I<dhpkey> value is
82 DH parameters are supplied in a B<DH> object instead in the I<dh> argument, and
84 should use "auto" parameters instead, or call SSL_CTX_set0_tmp_dh_pkey() or
87 An application may instead specify the DH parameters via a callback function
90 functions are deprecated. Applications should instead use "auto" parameters, or
91 specify the parameters via SSL_CTX_set0_tmp_dh_pkey() or SSL_set0_tmp_dh_pkey()
94 The callback will be invoked during a connection when DH parameters are
100 return the parameters to be used in a DH object. Ownership of the DH object is