Jeffrey Altman wrote: > > > When compiling an application with OPENSSL_LOAD_CONF defined, the > > macro maps to OPENSSL_add_all_algorithms_conf(), which additionally > > calls OPENSSL_config(NULL). This will automatically load the > > openssl.cnf file for engine configuration. The idea behind all this > > is that it is not necessary to change the source code for enabling > > engine configuration via openssl.cnf; it suffices to recompile with > > the application with OPENSSL_LOAD_CONF. > > Where is the openssl.cnf file expected to be found on Windows? >
The actual location is now determined by the function CONF_get1_default_config_file() and the openssl utility will be modified so everything goes through it. Currently this follows the same logic for finding openssl.cnf as the utilities. This results in the rather silly default of /usr/local/ssl/openssl.cnf but it can be overridden with the OPENSSL_CONF environment variable. CONF_get1_default_config_file() could be modified to do something more sensible under Windows: querying the registry perhaps? Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Gemplus: http://www.gemplus.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
