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 644214 - Seahorse should be a System Settings panel
Seahorse should be a System Settings panel
Status: RESOLVED WONTFIX
Product: seahorse
Classification: Applications
Component: general
git master
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2011-03-08 16:36 UTC by Cosimo Cecchi
Modified: 2012-03-15 10:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cosimo Cecchi 2011-03-08 16:36:47 UTC 
Long-term, Seahorse should probably be redesigned to be a System Settings panel. I think it would be nice to expose the keyring/certificate store as a core settings configuration.
Comment 1 Stef Walter 2011-03-08 17:21:38 UTC 
Where is the design of these panels taking place?
Comment 2 Stef Walter 2011-09-15 08:43:17 UTC 
I'm not necessarily against this, but are we sure we want all of the following as in system settings? 

 * PGP key management
 * SSH key management
 * Password management
 * Certificate Store
 * Smart card management

Would the above functionality be desirable in system settings? Or only a subset?

Note that some other OS's have a password/certificate/key manager separate from their system settings. For example Mac OS.
Comment 3 Akhil Laddha 2011-10-29 04:21:07 UTC 
Cosimo, do you have any comment on the proposal mentioned in comment#2 ?
Comment 4 André Klapper 2012-02-14 11:54:19 UTC 
Cosimo: Where is the design of these panels taking place?
Comment 5 Stef Walter 2012-02-14 13:25:20 UTC 
I think its here: https://live.gnome.org/Design/Apps/Credentials
Comment 6 Stef Walter 2012-03-15 10:40:09 UTC 
Seahorse won't become a panel. There will be further design changes to the application, but it does fit better as an auxiliary tool rather than into the panel itself. Obviously context specific password/key related functionality should be integrated into the appropriate places in the various panels.