RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2005936 - pkcs11: wpa_supplicant can't load shared library
Summary: pkcs11: wpa_supplicant can't load shared library
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: NetworkManager Development Team
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-20 14:04 UTC by David Jaša
Modified: 2022-03-23 11:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-22 09:27:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-97647 0 None None None 2021-09-20 14:04:47 UTC

Description David Jaša 2021-09-20 14:04:04 UTC 
Description of problem:
wpa_supplicant or openssl on el7 can't load PKCS#11 shared library

[probably not worth fixing but let's have it here for the record]


Version-Release number of selected component (if applicable):
NetworkManager-1.33.2-29238.copr.a8866095dd.el7.x86_64
wpa_supplicant-2.6-12.el7_9.2.x86_64
openssl-1.0.2k-21.el7_9.x86_64
softhsm-2.1.0-3.el7.x86_64

How reproducible:
always

Steps to Reproduce:
0. install softhsm, create nmci token with nmclient object with key and cert
1. get NetworkManager-ci, run 'sh prepare/hostapd.wired contrib/8021x/certs'
2. nmcli c add con-name con_pkcs11 type ethernet ifname test8X
3. nmcli c modify id con_pkcs11 autoconnect no 802-1x.eap tls 802-1x.identity test 802-1x.ca-cert /tmp/certs/test_user.ca.pem 802-1x.client-cert 'pkcs11:token=nmci;object=nmclient' 802-1x.client-cert-password-flags 4 802-1x.private-key 'pkcs11:token=nmci;object=nmclient?pin-value=1234' 802-1x.private-key-password-flags 4
4. nmcli c up id con_pkcs11

Actual results:
wpa_supplicant log:
SSL: Initializing TLS engine
ENGINE: engine pkcs11 not available [error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library]
TLS: Failed to set TLS connection parameters
ENGINE: engine deinit
EAP-TLS: Failed to initialize SSL.
EAP-TLS: Requesting private key passphrase  # <-- this is pointless, proper error should be reported back instead, see bug 2002572

Expected results:
wpa_supplicant uses the key and cert correctly

Additional info:
Comment 4 Fernando F. Mancera 2022-02-22 09:27:26 UTC 
pkcs11 is not supported in RHEL 7 and this is fixed on RHEL 8. Thanks!
Note You need to log in before you can comment on or make changes to this bug.