Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: ding@gnus.org,  tramp-devel@mail.freesoftware.fsf.org
Subject: Re: Passwords, stored in Gnome Keyring and KWallet
Date: Sat, 20 Mar 2010 14:47:27 -0500	[thread overview]
Message-ID: <87bpeibws0.fsf@lifelogs.com> (raw)
In-Reply-To: <87tysnq43l.fsf@gmx.de> (Michael Albinus's message of "Wed, 10 Mar 2010 22:06:06 +0100")

I tried to work on this but secrets.el was not usable on a recent Ubuntu
system (secrets-list-collections, for example, fails).  Can you explain
how to set it up or point me to a resource?
http://code.confuego.org/secrets-xdg-specs/ specified the protocol only
and I couldn't find a tutorial anywhere.

I comitted changes to the customization of auth-sources which would let
the user specify, in addition to the current "file" option expressed as
a string filename:

- a ':secrets' specifier, matching a host and a protocol and (optionally)
  a user name

- within each ':secrets' specifier, one of:

  - a collection name as a string

  - the 'default symbol (which we'll convert to a collection name with
    (secrets-get-alias "default") IIUC)

  - nil to indicate we don't have a valid collection and this specifier
    should be skipped (this helps with misconfigured specifiers)

  - t to indicate any collection is OK, we'll pick the first one
    returned by secrets-list-collections that matches the host, port,
    and username

  - the string "session" to indicate the temporary session-level
    collection

- optional parameters at the end of the spec, including a user name.  I
  may move the host and port to these optional parameters as well but
  I'm not sure if that's a good idea.  Comments welcome.

So this is about 30% done...

Thanks
Ted



  reply	other threads:[~2010-03-20 19:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 14:47 Michael Albinus
2010-02-22 20:41 ` Ted Zlatanov
2010-02-23 13:38   ` Michael Albinus
2010-02-23 20:03     ` Ted Zlatanov
2010-02-24  8:28       ` Michael Albinus
2010-03-09 16:50         ` Ted Zlatanov
2010-03-10 21:06           ` Michael Albinus
2010-03-20 19:47             ` Ted Zlatanov [this message]
2010-03-23 18:06             ` Ted Zlatanov
2010-03-23 18:23               ` Ted Zlatanov
2010-03-27 19:04               ` Ted Zlatanov
2010-03-29  5:00                 ` Katsumi Yamaoka
2010-03-29  6:51                   ` Norbert Koch
2010-03-29  7:04                     ` Katsumi Yamaoka
2010-03-29  7:48                       ` Norbert Koch
2010-03-29  9:26                   ` Ted Zlatanov
2010-05-12 12:07                 ` Michael Albinus
2010-05-12 12:30                   ` Ted Zlatanov
2010-05-12 13:06                     ` Michael Albinus
2010-05-16 18:39                     ` Michael Albinus
2010-05-18 19:50                       ` Michael Albinus
2010-06-07 16:28                       ` Ted Zlatanov
2010-06-08 13:55                         ` Michael Albinus
2010-06-07 16:41                   ` Ted Zlatanov
2010-06-08 13:56                     ` Michael Albinus
2010-06-08 14:34                       ` Ted Zlatanov
2010-03-11 11:46           ` Steinar Bang
2010-03-11 13:24             ` Ted Zlatanov

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=87bpeibws0.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=michael.albinus@gmx.de \
    --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).