asks to open keyring "default", but its pw was saved to "login"

Bug #762983 reported by ceg on 2011-04-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)
seahorse (Ubuntu)

Bug Description

Binary package hint: gksu

Gksu uses the keyring "default" and asks if that keyrings password should be saved to the "login" keyring.

Generally, it is a good idea to keep the gksu passwords locked in a separate keyring, not open all the time.

Still, gksu allows the user can select to save that keyring's password in the "login" keyring, that is usually open all the time.
With autologin, however, the "login" keyring is not open after login.

If the password for the keyring "default" was saved to "login", but the "login" keyring is not open, gksu should open the "login" keyring instead of the "default" keyring.

With this, the autologin behavior would come closer to the regular login behavior. The same credentials would be available after entering a single (and always the same) password.

ceg (ceg) wrote :

In ~/.gnome2/keyrings/ there seems to be a textfile "default" containing the string "login", pointing to the password store for "default.keyring".

summary: - asks to opens keyring "default", even though that pw was saved to
- "login"
+ asks to open keyring "default", but its pw was saved to "login"
ceg (ceg) wrote :

~/.gnome2/keyrings/default actually contains the name of the keyring that is marked as default ("login").

As gksu uses a separate keyring (named "default"), which is alright, it has to open the keyring used.
However, it should be able to ask for (open) a lower level keyring in case of daisy chained keyrings.

ceg (ceg) wrote :

Is it central functionality to handle keyring dependencies?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers