On Sat, 2007-02-24 at 19:05 -0900, John Andersen wrote:
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?
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? ------------ 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.
On this topic. It seems that KNetworkManager adopted the "NO config options for idiot users" approach of its Gnome ancestor. I need buttons to press and checkboxes to check dammit. Things I need to set myself: 1. Where to keep passwords 2. Edit config settings of wireless networks 3. Edit priority list of networks 4. Make dialup status indicator work and more... Today is the day I fire-up bugzilla. E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org