From d1f7a1e62a5b67b492f8e7eb48130bf00f9a3ab0 Mon Sep 17 00:00:00 2001 From: Matt Caswell Date: Thu, 26 Apr 2018 14:05:40 +0100 Subject: [PATCH] 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 (Merged from https://github.com/openssl/openssl/pull/6092) --- doc/man3/SSL_CTX_use_certificate.pod | 7 +++++++ 1 file changed, 7 insertions(+) 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. 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 or +L 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. -- 2.25.1