FS#37798 - [netctl] Profile with wpa key fails to start following upgrade to 1.4-1

Attached to Project: Arch Linux
Opened by Tom Sires (tsires) - Sunday, 17 November 2013, 02:24 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 14 January 2014, 06:05 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Urgent
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
netctl-auto fails to start my profile with a wpa key following update to 1.4-1 (from 1.3-1). I haven't tried it yet with other authentication types.

Everything works correctly after downgrading to 1.3-1.

Additional info:
This is my netctl config, minus the sensitive bits, which was generated automatically (I think) a few months ago. "Key" was originally a hexadecimal string of the same length:

Description='Home wifi (XXXXXXXX)'
Interface=wlp2s0
Connection=wireless
Security=wpa
ESSID=XXXXXXXX
IP=dhcp
Key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Logs, minus the sensitive bits again:

Nov 16 19:28:08 noodlebook netctl-auto[384]: Included profile 'wlp2s0-XXXXXXXX'
Nov 16 19:28:08 noodlebook netctl-auto[384]: Included profile 'wlp2s0-XXXXXXXXX'
Nov 16 19:28:08 noodlebook netctl-auto[384]: Included profile 'wlp2s0-XXXXXXXX'
Nov 16 19:28:08 noodlebook netctl-auto[384]: Successfully initialized wpa_supplicant
Nov 16 19:28:08 noodlebook netctl-auto[384]: Line 5: Invalid passphrase length 64 (expected: 8..63) 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"'.
Nov 16 19:28:08 noodlebook netctl-auto[384]: Line 5: failed to parse psk '"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"'.
Nov 16 19:28:08 noodlebook netctl-auto[384]: Line 8: failed to parse network block.
Nov 16 19:28:08 noodlebook netctl-auto[384]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlp2s0.conf'.
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 14 January 2014, 06:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in netctl 1.4-2 (in core)
Comment by Tom Sires (tsires) - Sunday, 17 November 2013, 03:54 GMT
Using netctl-git from the AUR fixes this problem for me.

This is the only commit since the 1.4 release, so it must be what fixes it:
https://projects.archlinux.org/netctl.git/commit/?id=3dc6d75f5fa4813fe5c998b13582912fffd88159
Comment by Jouke Witteveen (jouke) - Sunday, 17 November 2013, 08:15 GMT
https://mailman.archlinux.org/pipermail/arch-projects/2013-November/004001.html
Comment by James Duley (parched) - Tuesday, 19 November 2013, 00:37 GMT
So what do I need to change in my profile to make it work? "Key" to "key" and then back again once I get the patch?
EDIT: Actually I just manually edited /usr/lib/network/wpa in place, so I guess now I have 1.4-2 installed as 1.4-1.
Comment by Tom Sires (tsires) - Tuesday, 19 November 2013, 03:01 GMT
If you're changing your profile, a better solution might be to just prefix your hexadecimal key with \", according to the quoting rules at the end of netctl.profile(5), as described here:
https://bbs.archlinux.org/viewtopic.php?pid=1350597#p1350597

That should work fine both before and after a fixed version is released.
Comment by Martin Schmidt (Blind) - Saturday, 28 December 2013, 04:13 GMT
I have the same issue following a resume from suspend on my laptop (with and without profile change). It appears as if the dhcp client application fails to be restarted to get a new (or old) lease.

PS: Sorry, this is probably not the same issue. My WPA config is read just fine.

Loading...