Closed sharkcz closed 6 years ago
If i remember correctly, for this to work the shared object has to be installed to openssl ENGINESDIR (see openssl version -a) or the OPENSSL_ENGINES environment variable must specify the non-default ENGINESDIR (at least with upstream openssl). So the package could just install an engine.so symlink to ENGINESDIR.
However, i dont see a reason to not just rename the library. whats your opinion @dodys ?
one note - other engines already use the "non-lib" filename, at least on Fedora
I don't see any problem on changing the lib name. But I would appreciate if you could sign your commit before applying this commit. Thanks
updated
When the filename and engine name are the same (omitting the .so suffix), then it's possible to use the engine without configuration in openssl.conf (eg. "openssl speed -engine ibmca" works).