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 510106 - Store passwords in gnome-keyring
Store passwords in gnome-keyring
Status: RESOLVED WONTFIX
Product: conduit
Classification: Other
Component: core
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: conduit-maint@gnome.bugs
conduit-maint@gnome.bugs
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2008-01-17 08:44 UTC by John Stowers
Modified: 2018-07-11 23:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Experimental code to demonstrate using Gnome Keyring with Google Calender (5.87 KB, patch)
2008-04-15 02:04 UTC, nmarshall23
rejected Details | Review

Description John Stowers 2008-01-17 08:44:33 UTC
Which means we need a special way to identify them in get_config. Perhaps just make 

if fieldname == password
    store in keyring
else
    store in xml

(this bug was imported from trac)
Comment 1 nmarshall23 2008-04-15 02:04:42 UTC
Created attachment 109275 [details] [review]
Experimental code to demonstrate using Gnome Keyring with Google Calender

This is very Experimental code to show how to use Gnome Keyring with Google Calender. Adding support to other services would be simple, I just started with the one that bugged me the most.
Comment 2 John Stowers 2008-04-16 00:53:25 UTC
>  Currently I have trying to figure just how to add a custom widget to
>  the glade widget palette. It would be easier to add the key ring input
>  widget, to a dialog if it was in the glade palette. The documentation
>  on how to added widget to glade-2 is lacking thought..

Actually I would recommend against this. I dont really think its worth the effort. Its just as easy create the keyring widget code in the dataprovider and pack it into a vbox from the glade file as it is to do the object creation function business. In addition, I might be moving away from glade, to the gtk ui builder stuff this cycle (in an effort to reduce dependencies) so it would be beneficial not being too closely tied to glade.

I have been playing with your code some more, and am thinking that username/password keyring stuff could better fit as a proxy (or observer) around normal gtk.Entry/s. This way dataproviders could do something like (excuse pseudo code)

u = glade.get_widget(usename_entry)
pw = glade.get_widget(password_entry)

magic_password_entry = KeyringEntry(u,pw,;'google.com')

The magic_password_entry would be a normal gtk.Entry, but it would save/prepopulate its contents using the infomation in u (for the service google.com).

The same thing could also be accomplished with an observer type pattern that watches the username entry for changes, and fills in the password entry appropriately. Something like

key_magic = conduit.Settings.get_keyring_observer_singleton()
key_magic.do_magic(u,pw,'google.com')
Comment 3 André Klapper 2018-07-11 23:20:37 UTC
Conduit is not under active development anymore, has not seen code changes for eight years, and saw its last tarball release in 2010.
Its codebase has been archived: https://gitlab.gnome.org/Archive/conduit/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.