![](https://seccdn.libravatar.org/avatar/bba6bc4f91d8b9cb38fd49069a54dc85.jpg?s=120&d=mm&r=g)
Am Sonntag, 25. Februar 2007 05:05 schrieb John Andersen:
On Saturday 24 February 2007, Kai Ponte wrote:
I had the same issue for a year or so until I activated KWallet. I let KNetwork manager have access to KWallet and it now correctly connects to my WPA secured network rather than my neighbors' unsecured networks.
Mine has access to the wallet too.
(That is another issue that gripes me. Why should I have to run a passwordless wallet in order to allow boot time connection to wireless, and thereby putting all my personal settings and passwords at risk?
You can configure a system wide wifi connection using yast. NetworkManager will activate it on boot.
Why does knetworkmanager need to store wireless keys in a wallet? How secret do these things have to be? Why can't it store it in regular file with restrictive permissions?
Good point, I thougth about letting the user choose if he wants to store the keys unencrypted (e.g. in the knm config file or in a seperate passwordless wallet) a while ago too. Perhaps we get that into the next major release.
------------ But I digress..... Merely having the keys in the wallet does not seem sufficient to cause it to prefer the wet/wpa connections to the un-secured neighbors wifi.
Open the "show networks..." dialog and delete your neighbors networks. Only your's should stay. Helmut -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org