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 558734 - Bring back separate password memory options for VPNC connect dialog
Bring back separate password memory options for VPNC connect dialog
Status: RESOLVED DUPLICATE of bug 558331
Product: NetworkManager
Classification: Platform
Component: nm-applet
unspecified
Other All
: Normal minor
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-10-31 21:10 UTC by Josh North
Modified: 2008-11-01 03:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Comparison of 0.7.0 to 0.6.6 (56.94 KB, image/png)
2008-10-31 21:25 UTC, Josh North
Details

Description Josh North 2008-10-31 21:10:37 UTC
In a former version (6?) when connecting a Cisco VPN via nm-applet stored settings, there was a dialog box that allowed the user to check whether to remember each password (user and group).  Often, the user passwords change every session due to RSA or other token authentication, but the group password always remains the same.
As a user who logs in to several Cisco VPN sessions for work that use RSA authentication, it would be really cool to get that back!

Other information:
Once submitted, I'll see if I can add a screenshot comparison if this tool lets me add attachments.
Comment 1 Josh North 2008-10-31 21:25:41 UTC
Created attachment 121753 [details]
Comparison of 0.7.0 to 0.6.6

In this comparison, the 0.7.0 connect dialog is on the left, 0.6.6 is on the right.  The very bottom checkbox on the right-hand (0.6.6) dialog is what would be great to have back, the option to remember just the group password.
Comment 2 Dan Williams 2008-11-01 03:09:57 UTC
NetworkManager never had this patch.  Various distros carried a patch for a while (including Fedora) but it was a hack.  It'll get solved in a more elegant manner in the near future.

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