Vincent Untz wrote: > As to the seahorse/gnome-keyring-manager question: it might really be > confusing to have both of them in the long term. Is removing > gnome-keyring-manager a goal we can set for 2.20?
Yes, I believe so. Seahorse will be a simpler method for managing the gnome-keyring passwords. There are a few (mostly UI) issues yet to be resolved: * How to present changing the (gnome-keyring) 'master' password * The 'master' password should probably be tied (in the UI) to the user's login password (for easy use of pam-keyring). * Should we then also allow the user to change their login password through seahorse (ie: manage all passwords under one roof?) * Cached passwords for encryption keys should show up under the encryption key (ie: 'remember the password for this key') * Support multiple (gnome-keyring) keyrings? (probably not) Anyway all that to say: Yes by 2.20 we should have an easy to use replacement for gnome-keyring-manager. I hope the gnome-keyring-manager maintainers are okay with this... Cheers, Nate Nielsen _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
