NM saves WEP key in GNOME keyring and requires additional password

Bug #89096 reported by Paul Sladen
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: network-manager

On initial install, or when using the LiveCD after connecting to a wireless network requiring a hex WEP key, NM causes a GNOME keyring dialogue to be displayed demanding a password for protecting the WEP key.

  http://www.paul.sladen.org/ubuntu/bugs/feisty-20070301-bugs/nm-create-keyring-no-null-password.png

It is not possible to enter a blank/null password. The WEP key is not important enough to have it stored in a keyring protected by an additional passphrase.

Ideally NM would just store this in ~/.network-manager/ or somewhere convenient.

Changed in network-manager:
assignee: nobody → desktop-bugs
status: Unconfirmed → Confirmed
Revision history for this message
Mathias Hasselmann (hasselmm) wrote :

This dependency also causes another problem if your only connectivity is the WLAN card: As long as network-manager doesn't have setup that card there will be no DNS service. This will cause GNOME settings daemon to hang on startup. Unfortunatly this behaviour of GNOME settings daemon, also will cause network-manager not to startup.

Despite the fact, that this problem of the settings daemon - which should be solved - this example makes clear, that network manager should *CANNOT* store WEP keys in the keyring, when providing essential network services.

Revision history for this message
Mathias Hasselmann (hasselmm) wrote :

Maybe inclusion of libpam-keyring would solve this issue: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/54779

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.