Comment 3 for bug 738391

Revision history for this message
Markus Korn (thekorn) wrote :

I think at the end it's which caption clients like seahorse are using for each item in the keyring, keys are AFAIK not stored with any description.
seahorse seems to have three possible patterns for the description of a key, it's either of these:
  <server>
  <user>@<server>
  <user>@<server>/<object>
Or, if <server> is NULL and the item is a network password the phrase "network password" is used.

Launchpadlib (via python-keyring) is using these values ATM:
  user = 'System-wide: <dist-name> (<username>)@https://<lp-service-root>/'
  domain = 'launchpadlib'
The 'server' field is not used, this is why user of seahorse see the generic description.

So if launchpadlib simply uses some value for 'server' seahorse would show something usefull. Unfortunatly python-keyring's GnomeKeyring backend does not support using the "server" argument, so launchpadlib has to subclass this backend. I propose using this arguments:
  user = 'System-wide: <dist-name> (<username>)'
  server = '<lp-service-root>'
  domain = 'launchpadlib'

Implementing a subclass of the GnomeKeyring backend seems to be a bit hackish, but possible in a few lines of code.