Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: auth-source.el rewrite
Date: Sat, 29 Jan 2011 15:11:48 +0100	[thread overview]
Message-ID: <87y663hk9n.fsf@gmx.de> (raw)
In-Reply-To: <87ei7yumj2.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 27 Jan 2011 14:20:01 -0600")

Ted Zlatanov <tzz@lifelogs.com> writes:

> MA> Is it necessary to pass them as list with the keyword :create-extra-keys?
> MA> Just allow them to be added to SPEC, and if they don't belong to the
> MA> well known keywords, they are ignored during search, and used during
> MA> creation.
>
> The problem is that you don't know which SPEC keywords should be used
> for creation and some backends may not support some keywords.  I'd
> rather make it explicit, where there's a base list (for netrc: host user
> protocol secret) and the user can augment it.  That's also the only way
> to pass the default prompt, meaning a value we'd like to suggest to the
> user but which they can override.  For example this:
>
> (auth-source-search :host '("nonesuch" "twosuch") :type 'netrc :max 1
> :create t :create-extra-keys '((A "default A") (B)))

This results in 

Debugger entered--Lisp error: (void-variable A)
  symbol-value(A)
  (and (symbol-value r) (listp (symbol-value r)))

For me, the argument list looks a little bit ugly. Couldn't we merge at
least :create and :create-extra-keys, and use keys for the extra keys?
Something like

(auth-source-search :host '("nonesuch" "twosuch") :type 'netrc :max 1
:create '(:A "default A" :B))

The value for :create could also be t, when there are no extra
keys. :replace-existing could be a special key in the list, which is not
added to the new entry.

> MA> What about using password-cache? If a user does not like password
> MA> caching (for security reasons, or so), she could set password-cache to nil.
>
> MA> There is no need for an additional auth-source-do-cache then.
>
> Hmmm.  But we're caching more than the password.  It could work if the
> key was not required to be a valid symbol name, so it could be a
> serialized SPEC (the value doesn't have any restrictions).  Right now
> password-cache-* won't work.

Any string works as key. In Tramp, I do it similar (serializing method,
user, host, protocol). No big deal.

> Ted

Best regards, Michael.



  reply	other threads:[~2011-01-29 14:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25  2:59 nnimap-username Daiki Ueno
2010-10-25  6:33 ` nnimap-username Reiner Steib
2010-10-25  7:13   ` nnimap-username Daiki Ueno
2010-10-25 18:09     ` auth-source tokens (was: nnimap-username) Ted Zlatanov
2010-10-26 16:56       ` auth-source tokens Ted Zlatanov
2010-10-29  8:04         ` Michael Albinus
2010-10-29 22:15         ` Lars Magne Ingebrigtsen
2010-11-11 16:22           ` Ted Zlatanov
2010-11-14 17:24             ` Michael Albinus
2010-11-15  0:59               ` Ted Zlatanov
2010-11-15  4:47                 ` Michael Albinus
2010-11-15 15:14                   ` Ted Zlatanov
2010-11-15 16:03                     ` Michael Albinus
2011-01-24 17:27                       ` auth-source.el rewrite (was: auth-source tokens) Ted Zlatanov
2011-01-24 23:36                         ` auth-source.el rewrite Lars Ingebrigtsen
2011-01-25 16:59                           ` Ted Zlatanov
2011-01-25 21:09                             ` Michael Albinus
2011-01-25 21:42                               ` Ted Zlatanov
2011-01-26  8:32                                 ` Michael Albinus
2011-01-26 17:03                                   ` Ted Zlatanov
2011-01-26 19:35                                     ` Michael Albinus
2011-01-26 20:35                                       ` Ted Zlatanov
2011-01-26 22:15                                         ` Ted Zlatanov
2011-01-27 16:49                                           ` Michael Albinus
2011-01-27 20:20                                             ` Ted Zlatanov
2011-01-29 14:11                                               ` Michael Albinus [this message]
2011-01-31  2:49                                                 ` Ted Zlatanov
2011-01-31 14:30                                                   ` Michael Albinus
2011-01-31 17:09                                                     ` Ted Zlatanov
2011-01-27 12:35                                         ` Michael Albinus

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=87y663hk9n.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=ding@gnus.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).