From: Viktor Dukhovni Date: Mon, 17 Nov 2025 08:03:32 +0000 (+1100) Subject: Editorial: future proofing -> future-proofing X-Git-Tag: 4.0-PRE-CLANG-FORMAT-WEBKIT~146 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=98e8800e704e5c8caf6fab5871e22ceec758ee07;p=thirdparty%2Fopenssl.git Editorial: future proofing -> future-proofing Reviewed-by: Saša Nedvědický Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/28650) --- diff --git a/doc/designs/passing-algorithmidentifier-parameters.md b/doc/designs/passing-algorithmidentifier-parameters.md index f33862e45e2..9c5669e86b2 100644 --- a/doc/designs/passing-algorithmidentifier-parameters.md +++ b/doc/designs/passing-algorithmidentifier-parameters.md @@ -102,8 +102,8 @@ EVP_PKEY_CTX_get_algor_params(EVP_PKEY_CTX *ctx, X509_ALGOR *alg); EVP_PKEY_CTX_get_algor(EVP_PKEY_CTX *ctx, X509_ALGOR **alg); ``` -Note that all might not need to be added immediately, depending on if they -are considered useful or not. For future proofing, however, they should +Note that not all may need to be added at this time, depending on whether or +not they are considered useful. For future-proofing, however, they should probably all be added. Requirements on the providers diff --git a/doc/man3/SSL_CTX_config.pod b/doc/man3/SSL_CTX_config.pod index 8ddb4a9739a..9b1eb3e3267 100644 --- a/doc/man3/SSL_CTX_config.pod +++ b/doc/man3/SSL_CTX_config.pod @@ -18,9 +18,10 @@ B structure using the configuration B. By calling SSL_CTX_config() or SSL_config() an application can perform many complex tasks based on the contents of the configuration file: greatly -simplifying application configuration code. A degree of future proofing -can also be achieved: an application can support configuration features -in newer versions of OpenSSL automatically. +simplifying application configuration code. +Some future-proofing can be attained this way: the specified configuration +section can specify settings supported by the run-time version of OpenSSL that +were not known at the time the application code was written. A configuration file must have been previously loaded, for example using CONF_modules_load_file(). See L for details of the configuration