From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: tramp-devel@mail.freesoftware.fsf.org
Subject: Re: Secrets API "login" session is now "Login"?
Date: Mon, 14 Feb 2011 10:55:23 -0600 [thread overview]
Message-ID: <87aahysghw.fsf@lifelogs.com> (raw)
In-Reply-To: <87lj1ik4l6.fsf@gmx.de>
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)?
Ted
next prev parent reply other threads:[~2011-02-14 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 15:23 Ted Zlatanov
2011-02-14 15:39 ` Michael Albinus
2011-02-14 16:55 ` Ted Zlatanov [this message]
2011-02-14 20:36 ` Michael Albinus
2011-02-14 20:56 ` Ted Zlatanov
2011-02-14 21:11 ` Michael Albinus
2011-02-14 21:27 ` Ted Zlatanov
2011-02-14 21:50 ` Michael Albinus
2011-02-14 21:58 ` Michael Albinus
2011-02-14 22:09 ` Ted Zlatanov
2011-02-14 22:20 ` Michael Albinus
2011-02-15 13:48 ` Ted Zlatanov
2011-02-15 14:09 ` Michael Albinus
2011-02-15 15:19 ` Ted Zlatanov
2011-02-15 15:26 ` Michael Albinus
2011-02-14 21:46 ` Michael Albinus
2011-02-14 21:49 ` Ted Zlatanov
2011-02-14 22:01 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aahysghw.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=tramp-devel@mail.freesoftware.fsf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).