I modified my openssl.cnf to specify a custom engine for some operations. It works fine if I go through the openssl binary directly, but if I load libssl from another program it doesn't seem to use that configuration file at all, so my engine isn't available. I ultimately want the engine to be usable from Apache via mod_ssl. I think I can use the SSLCryptoDevice Apache configuration directive to specify which engine to use, but since it's not reading my OpenSSL configuration, it's not loading my custom engine, so it's not available for use. Is there some way to tell OpenSSL (either directly or, probably, through Apache) to load my engine?


Figured it out. If you build mod_ssl with -DOPENSSL_LOAD_CONF, it will load the configuration file the same as the openssl binary (I assume the binary is built with the same flag)

  • Since it came down to a compile option, what distro are you on? – Bratchley Jan 27 '15 at 14:35
  • @Bratchley Gentoo, although I was building Apache manually anyway – Michael Mrozek Jan 27 '15 at 15:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.