OPENSSL_config, OPENSSL_no_config - simple OpenSSL configuration functions

       Copyright 2004-2020 The OpenSSL Project Authors. All Rights Reserved.

       Licensed under the Apache License 2.0 (the "License").  You may not use this file  except  in  compliance
       with  the  License.   You  can  obtain  a  copy  in  the  file  LICENSE  in the source distribution or at
       <https://www.openssl.org/source/license.html>.

3.5.0                                              2025-06-04                               OPENSSL_CONFIG(3SSL)

OPENSSL_config() configures OpenSSL using the standard openssl.cnf and reads from the application section
       appname. If appname is NULL then the default section, openssl_conf, will be used.  Errors are silently
       ignored.  Multiple calls have no effect.

       OPENSSL_no_config() disables configuration. If called before OPENSSL_config() no configuration takes
       place.

       If the application is built with OPENSSL_LOAD_CONF defined, then a call to OpenSSL_add_all_algorithms()
       will implicitly call OPENSSL_config() first.

OPENSSL_CONF
           The path to the config file.  Ignored in set-user-ID and set-group-ID programs.

       The   OPENSSL_no_config()   and   OPENSSL_config()   functions   were  deprecated  in  OpenSSL  1.1.0  by
       OPENSSL_init_crypto().

       OPENSSL_config, OPENSSL_no_config - simple OpenSSL configuration functions

       The OPENSSL_config() function is designed to be a very simple "call it and forget it" function.  It is
       however much better than nothing. Applications which need finer control over their configuration
       functionality should use the configuration functions such as CONF_modules_load() directly. This function
       is deprecated and its use should be avoided.  Applications should instead call CONF_modules_load() during
       initialization (that is before starting any threads).

       There are several reasons why calling the OpenSSL configuration routines is advisable. For example, to
       load dynamic ENGINEs from shared libraries (DSOs).  However, very few applications currently support the
       control interface and so very few can load and use dynamic ENGINEs. Equally in future more sophisticated
       ENGINEs will require certain control operations to customize them. If an application calls
       OPENSSL_config() it doesn't need to know or care about ENGINE control operations because they can be
       performed by editing a configuration file.

       Neither OPENSSL_config() nor OPENSSL_no_config() return a value.

config(5), CONF_modules_load_file(3)

        #include <openssl/conf.h>

       The following functions have been deprecated since OpenSSL 1.1.0, and can be hidden entirely by defining
       OPENSSL_API_COMPAT with a suitable version value, see openssl_user_macros(7):

        void OPENSSL_config(const char *appname);
        void OPENSSL_no_config(void);