On Tue, Feb 26, 2002 at 09:50:43AM -0500, Jeffrey Altman wrote: > -OpenSSL_add_all_algorithms 508 EXIST::FUNCTION: > +OpenSSL_add_all_algorithms 508 NOEXIST::FUNCTION:
> +OPENSSL_add_all_algorithms_noconf 3212 EXIST::FUNCTION: > +OPENSSL_add_all_algorithms_conf 3213 EXIST::FUNCTION: > +OPENSSL_load_builtin_modules 3214 EXIST::FUNCTION: > +AES_ofb128_encrypt 3215 EXIST::FUNCTION:AES > +AES_ctr128_encrypt 3216 EXIST::FUNCTION:AES > +AES_cfb128_encrypt 3217 EXIST::FUNCTION:AES > > That OpenSSL_add_all_algorithms is no longer going to be exported. I > assume that it is being replaced by the _noconf and conf versions. > What is the distingtion between these functions and how is it > recommended that application developer's choose which one to use? OpenSSL_add_all_algorithms() now is a macro. By default it maps to OPENSSL_add_all_algorithms_noconf(), which is essentially the previuos OpenSSL_add_all_algorithms(). 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. -- Bodo M�ller <[EMAIL PROTECTED]> PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html * TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt * Tel. +49-6151-16-6628, Fax +49-6151-16-6036 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
