The new version of NetworkManager makes me enter my password to the GNOME keyring thingy before it will connect to the wireless network. The WEP key is a system-wide thing; that's why it's stored in /etc/sysconfig/network-scripts/key-eth1. NetworkManager ought to connect without user interaction, as it used to in FC4.
Created attachment 122641 [details] login prompt for NM
I reported something like this before in bug #172555 Hope to see it fixed some day :-)
*** This bug has been marked as a duplicate of 172555 ***
This is actually a really hard problem to solve. We can't let every user of a machine have access to one persons VPN, for instance. This same idea can be extended to access points (who's to say the access point is not connected to a local intranet only type thing?). This gets even more complicated when you factor in things like fast user switching. The bottom line is the problem is not going to get solved for FC5.
You already _do_ let every user of the machine access the VPN while it's up. You haven't played with iptables and per-user filtering, have you? That's a bogus argument. It would be fairly simple to put keys somewhere which are usable by NetworkManager in the absence of any given user. Ideally you'd use the keys which are always configured with system-config-network.
This seems to have got worse. Now I'm asked for the password every time my machine comes back from suspend-to-RAM.
This works for me with current rawhide - I'm asked for my password once and only once. David, can you confirm and either close this bug or move it to F8Target (so we can push for a proper solution next release)?
This is unlikely to see any action before f7 final.
I'm still asked for a password. Just once, but even that is too much, and is a regression since FC4.
Have you guys tried pam_keyring? The pam_keyring module unlocks gnome-keyring with the system password a user provides to log in.
*** This bug has been marked as a duplicate of 154652 ***