From: Jeff King <peff@peff.net>
To: John Szakmeister <john@szakmeister.net>
Cc: git@vger.kernel.org
Subject: Re: Credentials and the Secrets API...
Date: Thu, 27 Oct 2011 10:48:07 -0700 [thread overview]
Message-ID: <20111027174807.GD1967@sigill.intra.peff.net> (raw)
In-Reply-To: <CAEBDL5Udooim_3Za76Q1Rt_aGXtsSv76nxRegGWRBE=WJQzfZA@mail.gmail.com>
On Thu, Oct 27, 2011 at 12:05:03PM -0400, John Szakmeister wrote:
> Just wanted to keep folks in the loop. It turns out that the Secrets
> API is still to young. I asked about the format to store credentials
> in (as far as attributes), and got a response from a KDE developer
> that says it's still to young on their front. They hope to have
> support in the next release of KDE. But there's still the issue of
> what attributes to use.
Thanks for looking into this. That explains why I had such trouble
finding good documentation on it.
> With that information, I went ahead and created a
> gnome-credential-keyring that uses Gnome's Keyring facility. I still
> need to do a few more things (mainly run it against Jeff's tests), but
> it's generally working. Just wanted to keep folks in the loop.
> Hopefully, I can get patches out this weekend.
Great, I'm looking forward to reading it.
> Jeff: it would be really excellent to break out the various pieces. I
> think it would also be better to split the asking for passwords from
> the storing of passwords.
That's my current plan. I just need to stop dragging my feet on
re-rolling the series.
-Peff
next prev parent reply other threads:[~2011-10-27 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 16:05 Credentials and the Secrets API John Szakmeister
2011-10-27 17:48 ` Jeff King [this message]
2011-11-01 6:39 ` John Szakmeister
2013-02-07 14:46 ` Ted Zlatanov
2013-02-09 10:58 ` John Szakmeister
2013-02-20 17:01 ` Ted Zlatanov
2013-02-21 19:27 ` John Szakmeister
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=20111027174807.GD1967@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=john@szakmeister.net \
/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).