diff options
| author | Matt Caswell <matt@openssl.org> | 2018-04-26 14:05:40 +0100 |
|---|---|---|
| committer | Matt Caswell <matt@openssl.org> | 2018-04-26 16:39:55 +0100 |
| commit | d1f7a1e62a5b67b492f8e7eb48130bf00f9a3ab0 (patch) | |
| tree | 08b726f87a9c8ebea42dc41e5508659ed3b10818 | |
| parent | f80c864318ee86cf26492c6914299423cddbe229 (diff) | |
Update the *use_certificate* docs
Note that calling the *use_certificate* functions will replace any existing
certificate of the same type. The same thing applies for private keys.
Fixes #2147
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/6092)
| -rw-r--r-- | doc/man3/SSL_CTX_use_certificate.pod | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/man3/SSL_CTX_use_certificate.pod b/doc/man3/SSL_CTX_use_certificate.pod index 4dff79cee2..b065d8f9e5 100644 --- a/doc/man3/SSL_CTX_use_certificate.pod +++ b/doc/man3/SSL_CTX_use_certificate.pod @@ -170,6 +170,13 @@ L<SSL_CTX_set_default_passwd_cb(3)>. of view, it however does not make sense as the data in the certificate is considered public anyway.) +All of the functions to set a new certificate will replace any existing +certificate of the same type that has already been set. Similarly all of the +functions to set a new private key will replace any private key that has already +been set. Applications should call L<SSL_CTX_check_private_key(3)> or +L<SSL_check_private_key(3)> as appropriate after loading a new certificate and +private key to confirm that the certificate and key match. + =head1 RETURN VALUES On success, the functions return 1. |