On Tue, Feb 22, 2011 at 07:55:00PM +0000, Neil Jerram wrote: > Neil Jerram <[email protected]> writes: > > > Cool. This really isn't a problem, and it's great to see active > > development. Thomas - I'm not even sure it's worth your time > > investigating; it's easy enough to reenter passphrases. > > However, connection doesn't work. Iliwi says "CONNECTING ..." but > wpa_supplicant isn't running. If I then run wpa_supplicant by hand with > the iliwi-generated wpa_supplicant.conf, I see: > > root@om-gta02 /usr/bin # wpa_supplicant -ieth0 -c > ~/.config/iliwi/wpa_supplicant > .conf > Line 4: Invalid PSK 'TTTTTTTT'. > Line 4: failed to parse psk 'TTTTTTTT'. > Line 5: WPA-PSK accepted for key management, but no PSK configured. > Line 5: failed to parse network block. > Failed to read or parse configuration > '/home/root/.config/iliwi/wpa_supplicant.conf'. > > .config/iliwi/wpa_supplicant.conf contains: > > ctrl_interface=/var/run/wpa_supplicant > network={ > ssid="TALKTALK-AF54D9" > psk=TTTTTTTT > } > > (I've obviously changed my passphrase here.) > > If I add quotes around TTTTTTTT in .config/iliwi/wpa_supplicant.conf, > wpa_supplicant runs successfully. > > This seems like a pretty basic error, that should have been caught by > minimal testing. I wonder what let it through? (Perhaps it's more > complex than it looks, and depends on an unanticipated interaction of > several programs...)
There is a patch for this which I think went in to SHR-U. _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
