After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 337735 - Storing network keys without needing manual keyring access
Storing network keys without needing manual keyring access
Status: RESOLVED DUPLICATE of bug 331529
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.6.6
Other All
: Normal minor
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2006-04-08 19:10 UTC by Andrew Conkling
Modified: 2006-04-10 18:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andrew Conkling 2006-04-08 19:10:48 UTC 
I propose a method to store the password for protected network keys without
requiring user interaction.  Currently, when connecting to a protected network,
you need to type your password for the GNOME keyring before it can connect.

NetworkManager is NICE, and this would smooth out another kink to seamless
network connectivity.  Especially with laptops (which are often changing
networks and/or being rebooted), this interaction can be a hassle.

Other information:
This has been reported on Launchpad:
https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/34898.

Thereon was mentioned that 0.7 would feature non-keyring password storage, but I
could not find confirmation here.

Also, a workaround is mentioned using a PAM module to automatically unlock the
GNOME keyring, but that doesn't seem like an ideal fix.
Comment 1 Andrew Conkling 2006-04-08 19:14:21 UTC 
Ah, crap.  I just found the original bug that confirms the fix for 0.7.  This can be marked a duplicate.  I'm very sorry!
Comment 2 Teppo Turtiainen 2006-04-10 18:07:39 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 331529 ***