Description of Problem: When the SSLCryptoDevice (or StrongholdAccelerator) directive is used in httpd.conf but the hardware accelerator is not present, httpd does not start. Version-Release number of selected component (if applicable): N/A How Reproducible: Easily. Steps to Reproduce: 1. Set SSLCryptoDevice (or StrongholdAccelerator) in httpd.conf on a system without a hardware accelerator. 2. 3. Actual Results: httpd does not start. Expected Results: httpd starts without using hardware accelerator. Additional Information: Enhancement requested by Ergon Informatik (Switzerland). There is no mod_ssl component listed in the component input box so I chose openssl instead.
Possibly this should be a separate config directive, e.g. SSLSoftwareFallback On Some people might prefer it to be a fatal error if the crypto device doesn't work, rather than silently failing (and their web server suddenly becoming slow).
i'd be okay with letting it fall-back by default and just placing a large warning in the error log. I suspect a company would prefer to have their webserver come back up slow than not at all after a midnight Saturday reboot.
Stronghold 4.0 Cross Platform reached End of Life as of the end of December 2005. For more information or further options see: http://www.redhat.com/software/stronghold/