NM saves WEP key in GNOME keyring and requires additional password
Bug #89096 reported by
Paul Sladen
on 2007-03-02
This bug report is a duplicate of:
Bug #34898: NM requires keyring password to connect to WEP/WPA network.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
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://
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.
Cristian Aravena Romero (caravena)
on 2007-03-02
| Changed in network-manager: | |
| assignee: | nobody → desktop-bugs |
| status: | Unconfirmed → Confirmed |
| Mathias Hasselmann (hasselmm) wrote : | #1 |
| Mathias Hasselmann (hasselmm) wrote : | #2 |
Maybe inclusion of libpam-keyring would solve this issue: https:/
To post a comment you must log in.
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.