Bug 1465138
| Summary: | EAP-TLS broken with wpa_supplicant 2.6/openssl1.1 in fedora 26 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Ambroz <rebus> |
| Component: | wpa_supplicant | Assignee: | Beniamino Galvani <bgalvani> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | atigro, bbennett, bgalvani, blueowl, david.bell, dcbw, kaspar.tint, lkundrak, michel, reavertm, thecubic |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | wpa_supplicant-2.6-8.fc26 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-20 15:54:03 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
Michal Ambroz
2017-06-26 18:23:25 UTC
Getting similar error for the WiFi authenticated with user certificate (EAP-TLS). I guess it is the same issue. I can confirm that the patch https://bugs.archlinux.org/task/54233?getfile=15295 from the Archlinux https://bugs.archlinux.org/task/54233 works for the EAP-TLS over the wired network cable. For some reason the patch doesn't help with the WiFi network requesting EAP-TLS. Relevant bug in the openssl - https://github.com/openssl/openssl/issues/3594 (In reply to Michal Ambroz from comment #2) > For some reason the patch doesn't help with the WiFi network requesting > EAP-TLS. Hi, can you please attach logs for the failing wifi connection attempt? Thanks! Posted patch upstream: http://lists.infradead.org/pipermail/hostap/2017-June/037739.html (In reply to Beniamino Galvani from comment #4) > (In reply to Michal Ambroz from comment #2) > > For some reason the patch doesn't help with the WiFi network requesting > > EAP-TLS. > > Hi, can you please attach logs for the failing wifi connection attempt? > Thanks! Hello Beniamino, the log for the Wifi + EAP-TLS failing looks the same as for LAN EAP-TLS - it claims it is not possible to load the private key (although, when patched, the same private key is used for the LAN EAP-TLS access and that works). I have not checked the wpa_supplicant code yet, but I would guess the same patch might be required on more places. Michal Ambroz ====== here goes the log ================================================== Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6547] device (atheros0): Activation: (wifi) connection 'TEST_WIFI' has security, and secrets exist. No new secrets needed. Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6547] Config: added 'ssid' value 'TEST_WIFI' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6547] Config: added 'scan_ssid' value '1' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6547] Config: added 'key_mgmt' value 'WPA-EAP' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6547] Config: added 'eap' value 'TLS' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6548] Config: added 'fragment_size' value '1266' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6548] Config: added 'ca_cert' value '/home/username/.cert/username_20190227_cl.pem' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6548] Config: added 'private_key' value '/home/username/.cert/username_20190227_key.pem' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6548] Config: added 'private_key_passwd' value '<hidden>' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6548] Config: added 'client_cert' value '/home/username/.cert/username_20190227_ca.pem' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6549] Config: added 'identity' value 'John Doe' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6549] Config: added 'bgscan' value 'simple:30:-65:300' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.6549] Config: added 'proactive_key_caching' value '1' Jul 03 15:36:49 notebook.domain.xy NetworkManager[1456]: <info> [1499089009.7577] device (atheros0): supplicant interface state: inactive -> scanning Jul 03 15:36:50 notebook.domain.xy wpa_supplicant[26270]: atheros0: SME: Trying to authenticate with 11:22:33:44:55:66 (SSID='TEST_WIFI' freq=2462 MHz) Jul 03 15:36:51 notebook.domain.xy kernel: atheros0: authenticate with 11:22:33:44:55:66 Jul 03 15:36:51 notebook.domain.xy kernel: atheros0: send auth to 11:22:33:44:55:66 (try 1/3) Jul 03 15:36:51 notebook.domain.xy kernel: atheros0: authenticated Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: Trying to associate with 11:22:33:44:55:66 (SSID='TEST_WIFI' freq=2462 MHz) Jul 03 15:36:51 notebook.domain.xy NetworkManager[1456]: <info> [1499089011.2341] device (atheros0): supplicant interface state: scanning -> authenticating Jul 03 15:36:51 notebook.domain.xy kernel: atheros0: associate with 11:22:33:44:55:66 (try 1/3) Jul 03 15:36:51 notebook.domain.xy kernel: atheros0: RX AssocResp from 11:22:33:44:55:66 (capab=0x431 status=0 aid=2) Jul 03 15:36:51 notebook.domain.xy kernel: atheros0: associated Jul 03 15:36:51 notebook.domain.xy NetworkManager[1456]: <info> [1499089011.2520] device (atheros0): supplicant interface state: authenticating -> associating Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: Associated with 11:22:33:44:55:66 Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: CTRL-EVENT-EAP-STARTED EAP authentication started Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=43 -> NAK Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13 Jul 03 15:36:51 notebook.domain.xy NetworkManager[1456]: <info> [1499089011.2844] device (atheros0): supplicant interface state: associating -> associated Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: OpenSSL: tls_read_pkcs12 - Failed to use PKCS#12 file error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: OpenSSL: pending error: error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: OpenSSL: tls_connection_private_key - Failed to load private key error:00000000:lib(0):func(0):reason(0) Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: TLS: Failed to load private key '/home/username/.cert/username_20190227_key.pem' Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: TLS: Failed to set TLS connection parameters Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: EAP-TLS: Failed to initialize SSL. Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS) Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CZ Jul 03 15:36:51 notebook.domain.xy wpa_supplicant[26270]: atheros0: CTRL-EVENT-EAP-FAILURE EAP authentication failed Jul 03 15:36:51 notebook.domain.xy kernel: atheros0: Limiting TX power to 4 dBm as advertised by 11:22:33:44:55:66 Jul 03 15:36:53 notebook.domain.xy wpa_supplicant[26270]: atheros0: Authentication with 11:22:33:44:55:66 timed out. Can this be hotfixed please? It breaks 802.1x on wired connections as well so upgrading kicks systems off of secured networks. I've applied the upstream patch to the RPM and confirmed that it restores wireless connections. Thanks! (In reply to David Carlson from comment #7) > Can this be hotfixed please? It breaks 802.1x on wired connections as well > so upgrading kicks systems off of secured networks. I've applied the > upstream patch to the RPM and confirmed that it restores wireless > connections. Thanks! Does the patch fix the problem with wired 802.1x connections for you? (In reply to Beniamino Galvani from comment #8) > Does the patch fix the problem with wired 802.1x connections for you? Yes - confirmed it fixes wired 802.1x on two different systems this morning. -Dave I can also confirm that archlinux patch fixes this issue. Looks like this was applied upstream: http://lists.infradead.org/pipermail/hostap/2017-July/037796.html https://w1.fi/cgit/hostap/commit/?id=f665c93e1d28fbab3d9127a8c3985cc32940824f wpa_supplicant-2.6-8.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c3438ec82a *** Bug 1471728 has been marked as a duplicate of this bug. *** wpa_supplicant-2.6-8.fc26 has been pushed to the Fedora 26 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-2017-c3438ec82a wpa_supplicant-2.6-8.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |