On Mon, 8 Jul 2002, Robert McMonigal wrote: > I have been trying to get an aep hardware acclerator to work under apache > 2.0.39. Everything installs fine and it runs fine with SSLCryptoDevice > builtin. But if I change builtin to aep and try to start it, it appears to > start mormally (no error messages from the console) but in the error log I > get "Init: Failed to enable Crypto Device API `aep'" I know the card is > working because I can do openssl speed rsa1024 -engine aep and the CPU time > is less then a second for ten seconds of computations. I have tried this on > redhat 7.3 and it works. So I was wondering if apache 2 compiles > differently on freebsd then redhat. Any ideas on what is going wrong would > be greatly appreciated. > > > I run the following command for the configure > > CFLAGS="-DSSL_EXPERIMENTAL -DSSL_ENGINE" ./configure > --prefix=/usr/local/httpd --enable-ssl > --with-ssl=/usr/local/src/openssl-engine-0.9.6d
Can you ensure you've got a decent debugging level set (eg. perhaps "SSLLogLevel info") and post the last few lines of the error log when starting up apache? That should include the openssl-generated error stack which will go some way further to saying how/why the initialisation failed. I'd suspect it's a failure to load the AEP-specific shared-library (ie. a path issue) but without more info it's difficult to tell. BTW: I assume you've verified that when you say "openssl speed rsa1024 -engine aep" is working, that you're talking about the copy of the 'openssl' binary in /usr/local/src/openssl-engine-0.9.6d and *not* the 'openssl' binary installed in a system $PATH as part of the freebsd distribution? If not, you're comparing success with one (packaged, installed, and quite possibly modified) build of openssl with failure of an entirely different build of openssl. Cheers, Geoff ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
