Public bug reported:
Affecting Dapper and if memory serves right, Breezy, too: While fighting
with my wireless card, ndiswrapper and the tool to set up wireless
network cards in gnome, I did:
# iwconfig wlan0 essid <something> key s:<passphrase>
and got no connection because I have a space character in my WEP
passphrase. When I escaped s:<passphrase> like so:
# iwconfig wlan0 essid <something> key "s:<passphrase>"
I got it working.
I then used the gnome network configuration tool
("Netzwerkeinstellungen" in german) to permanently write the
configuration to the system files. Rebooted, and got no connection, with
the same effects I had when I manually configured the WLAN card using
iwconfig.
I looked into /etc/network/interfaces, found that the passphrase after
the statement "wireless-key" was not escaped, escaped it, rebooted, and
voila it worked.
I suggest not to generally put the key in quotes in the configuration
file, but to correct the program which configures the WLAN-interface
using the configuration file.
ATTENTION: There may be security and safety implications with this too,
as "abc; rm -rf /" is a possible ASCII WEP security key (assuming
something like ifup calls iwconfig via the shell). I'm currently happy
to have my WLAN card working so I'm not gonna try it out myself ;)
** Affects: gnome-system-tools (Ubuntu)
Importance: Medium
Assignee: Ubuntu Desktop Bugs
Status: Confirmed
--
wireless-key from /etc/network/interfaces not escaped
https://launchpad.net/bugs/50386
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
