CONF_modules_load_file.pod: The ssl_module no longer uses global data

Remove the paragraph that is no longer relevant.

Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/29374)
This commit is contained in:
Daniel Kubec
2025-12-11 00:26:46 +01:00
committed by Tomas Mraz
parent fed15f076f
commit 3a6b9eb055

View File

@@ -162,12 +162,6 @@ context.
Therefore, even if used with a freshly created library context, the function
is not thread safe, and should not be used except as part of early application
initialisation.
Applications that want to use multiple library contexts may find that the most
recently loaded configuration file perturbs prior settings in other library
contexts.
For example, B<ssl> module settings are not library context specific, and the
last configuration file loaded that has an C<ssl_config> setting changes the
SSL settings for all library contexts.
The L<SSL_CTX_config(3)> and L<SSL_config(3)> functions can be used to perform
late customisation of SSL contexts and connection handles.
Here I<late> means that the chosen section's settings are applied in addition