Bug 1565836

Summary:	The epel-testing version libp11-0.4.7-3.el7.x86_64 breaks openssl engine pkcs11 on el7.4
Product:	Red Hat Enterprise Linux 7	Reporter:	Dave Dykstra <dwd>
Component:	libp11	Assignee:	Stef Walter <stefw>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	ansasaki
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-12 09:07:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave Dykstra 2018-04-10 21:20:01 UTC

Description of problem:

I tried installing libp11-0.4.7-3.el7.x86_64 and corresponding engine_pkcs11, and running "openssl engine pkcs11" failed.


Version-Release number of selected component (if applicable):
libp11-0.4.7-3


How reproducible:
Very

Steps to Reproduce:
1. install libp11 and engine_pkcs11 version 0.4.7-3.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

Comment 2 Dave Dykstra 2019-07-08 18:56:43 UTC

This problem still exists in 0.4.8.

Comment 3 Dave Dykstra 2019-07-08 19:41:45 UTC

Ticket replaced by #1728011.

Please close this bug, I don't seem to have an option to do that.

Comment 4 Anderson Sasaki 2019-08-12 09:07:33 UTC


*** This bug has been marked as a duplicate of bug 1728011 ***