On Mon, Jul 19, 2010, David Woodhouse wrote: > On Mon, 2010-07-19 at 18:26 +0200, Dr. Stephen Henson wrote: > > It should work without that if the application explicitly sets the crypto > > ENGINE to use for example with the SSLCryptoDevice directive in mod_ssl or > > via > > autoconf. > > It should, but obviously that's not a viable solution in the general > case. > > You shouldn't need to explicitly reconfigure all applications just to > make a library use a core CPU feature like SSE or AESNI. The library > should get that right for itself. > > OpenSSL *does* get that right for SSE, but not (yet) for AESNI. > Hence RT#2045. >
This issue could crop up for other ENGINEs in future. Adding a call to ENGINE_register_all_complete() at the end of ENGINE_load_builtin_engines() should resolve #2045 and any future cases. Can you confirm that please? Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
