Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: tramp-devel@mail.freesoftware.fsf.org, ding@gnus.org
Subject: Re: Passwords, stored in Gnome Keyring and KWallet
Date: Mon, 07 Jun 2010 11:41:59 -0500	[thread overview]
Message-ID: <8739wy3ico.fsf@lifelogs.com> (raw)
In-Reply-To: <87r5lhb9wl.fsf@gmx.de> (Michael Albinus's message of "Wed, 12 May 2010 14:07:54 +0200")

On Wed, 12 May 2010 14:07:54 +0200 Michael Albinus <michael.albinus@gmx.de> wrote: 

MA> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Michael, I left a TODO in the manual for explaining secrets.el.

MA> I'm sitting with this, it is not so easy.

MA> The crucial point is how to populate the Gnome Keyring with valid
MA> entries. For .authinfo files it is obvious, "edit the file".

Maybe assistant.el could be useful?  This is a good simple task: set up
auth-source entries for various types of accounts.  The manual doesn't
have to explain as much then, and the .ast file can describe the
secrets.el steps to create and populate a Secrets API backend.

If not, it becomes a pretty complicated explanation as you saw.  What
direction would you prefer?

MA> Consequently, auth-source.el shall offer such an interface. Something
MA> like (auth-source-create)
...
MA> What do you think about?

I agree 100% with your changes to auth-source.el you posted previously
to make this interface a possibility.  Deleting and creating
authinfo/netrc entries, which is missing in your version, should not be
too hard: we just need to remember the original line for every parsed
entry in netrc.el (to avoid cases where the parser might create
identical parses for two different lines).

Thank you
Ted

  parent reply	other threads:[~2010-06-07 16:41 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
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 [this message]
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=8739wy3ico.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).