moonshot-ui ignores identities.txt when displaying identities

[Stefan Paetow]

When you have identities both in the keyring and in the identities.txt file, moonshot-ui appears to ignore the identities stored in identities.txt.

Example:

1. Create identity in the Moonshot UI. It is stored in the Keyring.
2. Create a copy of the identity in an XML file, import it with moonshot-webp -f. An identities.txt is created.
3. Open Moonshot UI by running 'Moonshot.

You *should* have three entries, i.e. the 'No identity' identity, the credential you manually created in the UI and the one from identities.txt. There will only be two, the 'No Identity' identity and the one stored in the keyring. This should not be the case.

[Sam Hartman (hartmans)]

Most of this is expected behavior.
If you use gnome-keyring, you only use gnome-keyring.
If DISPLAY is set and you don't use the -f argument, moonshot-webp
should stick the identity into the keyring, not into identities.txt.

The -f argument forces identities.txt.

If you're seeing different behavior out of moonshot-webp that might be a
bug.

--Sam

[Stefan Paetow (stefan-paetow)]

Ok... this causes a synchronicity issue, i.e. if you are using an X environment, then of course the keyring is fine, but if you are in a non-X environment, i.e. pure text, the keyring is useless, but identities.txt works (provided your name is in the /etc/moonshot/flatfile-users list). There has to be a way to either synchronise this, or this is a user nightmare (which one of the sites *is* going to experience).

[Sam Hartman (hartmans)]

One possibility would be to arrange via pam to have a dbus and gnome-keyring in all sessions. Or to launch moonshot-ui itself with identities.txt. But this is a fairly important security design. If you have a user session with real user credentials not an automated service, then we want to find a way to use some implementation of the secret interface (what gnome-keyring is based on) all the time.