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

Ted Zlatanov <tzz@lifelogs.com> writes:

> I agree 100% that this is useful.  Why not allow authinfo editing too?
> I think auth-source-create should just be a wrapper for
>
> ;;; 'create-if-missing should be supplemented by a global
> ;;; auth-source-create-if-missing which could be 'never, 'always, or nil
> (auth-source-user-or-password "password" server port user 'create-if-missing)

D'accord. Maybe we dont't need `auth-source-create-if-missing'; the last
arg `create-if' missing could be t or nil.

> and it would (theoretically) work for any editable backend.  At least
> for the two backends we've discussed (Secrets API and flat netrc files)
> this would work.  That would give us a stateless way to ensure that a
> password exists, prompting the user if necessary without interrupting
> the code flow, and allowing the user to specify their preference as well
> if they want to always or never create entries.

OK. We have a long weekend here in Germany (next 4 days); maybe I try an
implementation. I want to understand your code anyway :-)

> Ted

Best regards, Michael.

  reply	other threads:[~2010-05-12 13:06 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 [this message]
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=nqk4r95kwu.fsf@alcatel-lucent.com \
    --to=michael.albinus@gmx.de \
    --cc=ding@gnus.org \
    --cc=tramp-devel@mail.freesoftware.fsf.org \
    --cc=tzz@lifelogs.com \
    /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).