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 755567 - Store password in my keychain with Seahorse
Store password in my keychain with Seahorse
Status: RESOLVED DUPLICATE of bug 709982
Product: polari
Classification: Applications
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Polari maintainers
Polari maintainers
Depends on:
Blocks:
 
 
Reported: 2015-09-24 19:24 UTC by Moo
Modified: 2015-09-24 21:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Moo 2015-09-24 19:24:05 UTC 
When I register my nickname with NickServ, how am I supposed to remember the password?
Save it to my keychain in GNOME Seahorse!

Authenticate to NickServ using my password from GNOME Seahorse!
Comment 1 Florian Müllner 2015-09-24 21:19:18 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 709982 ***
Comment 2 Moo 2015-09-24 21:26:18 UTC 
Note this is not just basic NickServ identification support.

This especially refers to NickServ authentication using tight integration with GNOME by means of using the keychain in GNOME Seahorse.
Comment 3 Florian Müllner 2015-09-24 21:40:11 UTC 
(In reply to Moo from comment #2)
> Note this is not just basic NickServ identification support.

OK, let me clarify then:
When we get support for NickServ authentification then yes, the credentials should be stored in the keyring via libsecret. But first we need to figure out how to best add that support without throwing crazy options at the user ;-)
Comment 4 Moo 2015-09-24 21:42:07 UTC 
Yeah, I wanted to clarify that since NickServ authentication could be implemented without the use of keyring.

So depending on the implementation (which may be a gradual implementation in multiple steps with an initial partial implementation) this may not be a duplicate since it covers a specific implementation.