Re: Secrets API "login" session is now "Login"?

[Ted Zlatanov <tzz@lifelogs.com>]

On Mon, 14 Feb 2011 21:36:55 +0100 Michael Albinus <michael.albinus@gmx.de> wrote: 

MA> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Mon, 14 Feb 2011 16:39:49 +0100 Michael Albinus
>> <michael.albinus@gmx.de> wrote:
>> 
MA> Ted Zlatanov <tzz@lifelogs.com> writes:
>>>> This morning I noticed that while seahorse told me the login collection
>>>> was "login", the Secrets API listed it as "Login".  I'm 100% sure that
>>>> it used to be "login".
>>>> 
>>>> I've adjusted auth-source.el and auth.texi accordingly.  If that's
>>>> wrong, please let me know.
>> 
MA> The Secret Service API does not speak about the "login" collection. The
MA> only promise it gives is the "default" alias:
>> 
MA> "Client applications without special requirements should store in the
MA> default collection. The default collection is always accessible through
MA> a specific object path."
>> 
>> OK, but I see "login" in Seahorse and "Login" from secrets.el.  There's
>> some disagreement happening.  Do you see that or is it just me (recent
>> Ubuntu system, dist-upgraded 2 weeks ago and updated regularly)?

MA> I'm running an up-to-date Ubuntu 10.10. In secrets.el, I see

MA>    (secrets-get-alias "default")
MA>     => "login"

MA> Maybe you have changed the default alias via `secrets-set-alias'?

No, I'm sure.

(secrets-get-alias "default")
=> nil

(secrets-list-collections)
=> ("session" "Login")

MA> Anyway, I recommend to use the collection returned by (secrets-get-alias
MA> "default"). There's is no need to hardwire it as "login".

We use "Login" in many of the examples.  I wanted a collection that may
actually have entries from other programs.  It's just puzzling that
"login" worked until recently and seahorse still says "login".

Ted