GNOME Bugzilla – Bug 643885
The procedure the change the master password is too complex
Last modified: 2018-08-03 19:20:11 UTC
Forwarded from https://bugs.launchpad.net/bugs/498465 The procedure to change gnome keyring's password is too complex. Opening a folder properties and then selecting "Change password" is not a common way to change a master password for an application/system. Evidence that this a common issue: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/449464 http://ubuntuforums.org/showthread.php?t=157808 http://www.code-muse.com/blog/?p=53
In general this should not be necessary for normal users to do. 1. The login keyring password should be kept in sync with the user's unix password. This occurs automatically when a proper password changing tool (such as 'passwd') is used. The tool needs to use the standard PAM facilities to change the user's password. 2. Even if the password gets out of sync, gnome-keyring-2.91.1 and later helps to fix the user's password when it gets out of sync. The first time its detected that the password for the login keyring and user's unix password are out of sync, the user is prompted to enter their old password, and the login keyring is then changed to the new password. If there are additional design changes that are suggested, please add them to this ticket.
Andreas, ping, any response for comment#1 ?
Stef, shall we remove needinfo if it's a valid issue ?
I haven't heard back from the original reporter on LP, so this is my opinion: There should be a "Change Password"-Button when I double-click on a keyring. This problem doesn't arise with the login-keyring (as stef described), but with additional keyrings.
Note that there is already a "Change Passphrase" when you doubleclick to go to the preferences of a ssh or pgp-key so it's logical to look there for this option.
Andreas, sounds like a good plan. Are you thinking of putting together a patch which does this?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/53.