Bug 1471728

Summary: [wpa_supplicant] TLS: Failed to load private key
Product: [Fedora] Fedora Reporter: Veske <kaspar.tint>
Component: wpa_supplicantAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 26CC: bgalvani, blueowl, dcbw, kaspar.tint, lkundrak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-17 19:13:27 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:
Attachments:
Description Flags
wpa_supplicant error logs none

Description Veske 2017-07-17 10:51:17 UTC 
Created attachment 1299780 [details]
wpa_supplicant error logs

Description of problem:

After update to Fedora 26, my connection to private network though TLS does not work anymore. wpa_supplicant is throwing errors shown in the attachment.


Version-Release number of selected component (if applicable):
OpenSSL 1.1.0f-fips  25 May 2017
wpa_supplicant v2.6

How reproducible:

Attempt to make a TLS connection though NetworkManager Gnome applet and look at wpa_supplicant logs when establishing connection.


Actual results:
Connection fails with error TLS: Failed to load private key

Expected results:
Connection should work like it did in Fedora 25.

Additional info:

I found a similar bug on Archlinux bug tracker: https://bugs.archlinux.org/task/54233

It seems that the Arch Linux maintainers fixed the issue already and released the new version for wpa_supplicant. Would be great to have this fix on Fedora also.
Comment 1 Veske 2017-07-17 11:05:46 UTC 
I was able to work around this bug by removing passphrase from my private key. This is not a very good solution tough and I think this issue should be resolved.
Comment 2 Beniamino Galvani 2017-07-17 19:13:27 UTC 

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