git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Credentials and the Secrets API...

From
John Szakmeister <john@szakmeister.net>
Date
Feb 9, 2013, 10:58 UTC
Message-ID
<CAEBDL5VQxhnL+wdkf_5=MmG4ptBr4TFyyAvbMWxRom9SRxJ6Lg@mail.gmail.com>
In-Reply-To
<87halochci.fsf@lifelogs.com>
On Thu, Feb 7, 2013 at 9:46 AM, Ted Zlatanov <tzz@lifelogs.com> wrote:
Show 17 quoted lines
> On Thu, 27 Oct 2011 12:05:03 -0400 John Szakmeister <john@szakmeister.net> wrote:
>
> JS> Just wanted to keep folks in the loop.  It turns out that the Secrets
> JS> API is still to young.  I asked about the format to store credentials
> JS> in (as far as attributes), and got a response from a KDE developer
> JS> that says it's still to young on their front.  They hope to have
> JS> support in the next release of KDE.  But there's still the issue of
> JS> what attributes to use.
>
> JS> With that information, I went ahead and created a
> JS> gnome-credential-keyring that uses Gnome's Keyring facility.  I still
> JS> need to do a few more things (mainly run it against Jeff's tests), but
> JS> it's generally working.  Just wanted to keep folks in the loop.
> JS> Hopefully, I can get patches out this weekend.
>
> Do you think the Secrets API has matured enough?  KDE has had a new
> release since your post...

Yes, I think it has. Several other applications appear to be using it, including some things considered "core" in Fedora--which is a good sign.

-John
Previous: Ted ZlatanovNext: Ted Zlatanov
Message 5 of 7 in “Credentials and the Secrets API...”
  1. John SzakmeisterOct 27, 2011
  2. Jeff KingOct 27, 2011
  3. John SzakmeisterNov 1, 2011
  4. Ted ZlatanovFeb 7, 2013
  5. John SzakmeisterFeb 9, 2013
  6. Ted ZlatanovFeb 20, 2013
  7. John SzakmeisterFeb 21, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.