Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I long ago misfiled this as bug #1565836 under the old name of the package, libp11 and under RHEL instead of Fedora EPEL. Bugzilla won't let me change the product, so I am creating a new ticket. Running "openssl engine pkcs11" with openssl-pkcs11-0.4.8-1.el7.x86_64 fails. Version-Release number of selected component (if applicable): 0.4.8-1.el7 How reproducible: Very Steps to reproduce: 1. install openssl-pkcs11-0.4.8-1.el7 2. run "openssl engine pkcs11" Actual results: 140280849905568:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(/usr/lib64/openssl/engines/libpkcs11.so): /usr/lib64/openssl/engines/libpkcs11.so: cannot open shared object file: No such file or directory 140280849905568:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 140280849905568:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:467: 140280849905568:error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:392:id=pkcs11 Expected results: (pkcs11) pkcs11 engine Additional info: Workaround: ln -s /usr/lib64/engines-1.1/pkcs11.so /usr/lib64/openssl/engines ln -s /usr/lib64/engines-1.1/libpkcs11.so /usr/lib64/openssl/engines
I made a pull request to fix this for version 0.4.10: https://src.fedoraproject.org/rpms/openssl-pkcs11/pull-request/6
FEDORA-EPEL-2019-84cd252eb9 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-84cd252eb9
openssl-pkcs11-0.4.10-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-84cd252eb9
openssl-pkcs11-0.4.10-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1565836 has been marked as a duplicate of this bug. ***