Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18405 - [netcfg] fails to parse wpa passphrase with backslash
Attached to Project:
Arch Linux
Opened by lornoss (lornoss) - Saturday, 20 February 2010, 00:37 GMT
Last edited by James Rayner (iphitus) - Sunday, 21 February 2010, 04:04 GMT
Opened by lornoss (lornoss) - Saturday, 20 February 2010, 00:37 GMT
Last edited by James Rayner (iphitus) - Sunday, 21 February 2010, 04:04 GMT
|
DetailsDescription:
Backslashes need to be preceded by a double backslash in network profile in order for netcfg to build a correct wpa_supplicant config. I believe this is a new behavior as of netcfg 2.5 and this needs to be noted in documentation if this is intentional. Additional info: * 2.5.2 /etc/network.d/routulator: CONNECTION="wireless" INTERFACE="wlan0" SECURITY="wpa" ESSID="routulator" IP="dhcp" KEY="<passphrase with a backslash>" |
This task depends upon
Closed by James Rayner (iphitus)
Sunday, 21 February 2010, 04:04 GMT
Reason for closing: Fixed
Additional comments about closing: documented on wiki, will modify examples to use single quotes where appropriate.
Sunday, 21 February 2010, 04:04 GMT
Reason for closing: Fixed
Additional comments about closing: documented on wiki, will modify examples to use single quotes where appropriate.
Comment by Jan de Groot (JGC) -
Saturday, 20 February 2010, 02:08 GMT
As netcfg uses bash syntax, the need to escape backslashes inside double quotes is completely normal. Enclosing the key in single quotes would also fix your issue.