From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: auth-sources asking for password 2 or 3 times
Date: Wed, 23 Feb 2011 08:54:09 -0600 [thread overview]
Message-ID: <87wrkqol7y.fsf@lifelogs.com> (raw)
In-Reply-To: <m3y657xlm7.fsf-ueno@unixuser.org>
On Wed, 23 Feb 2011 16:20:48 +0900 Daiki Ueno <ueno@unixuser.org> wrote:
DU> I agree with that it might be hard for users to maintain two files.
DU> However, you seem to be missing the point of my idea, FWIW, here is the
DU> detail:
DU> If auth-source.el looks for several parameters (say,
DU> user/host/port/password) to establish a connection, it needs to decrypt
DU> ~/.authinfo.gpg (at least) 4 times if cache is disabled (right?).
Not anymore. If someone uses the old API
(`auth-source-user-or-password') 4 times then yes.
DU> However, if we store user/host/port/token in a plain text file (say,
DU> ~/.netrc), and store token/password mapping in an encrypted file (say,
DU> ~/.passwords.gpg), auth-source.el needs to decrypt the latter file only
DU> once.
I see. That seems to me a bit inconvenient: now the user has to manage
two files and keep them in sync. But I think I understand you're trying
to separate connection parameters (everything but the :secret token)
from the secrets themselves. Hmm. How about a new spec in auth-sources
like this:
"~/.netrc+~/.authinfo.gpg"
which would look in netrc for all the non-secret things and then in the
second file for the secrets?
DU> In other words, my idea is to delay decryption until password is really
DU> necessary. This is useful when accessing password-less news servers
DU> (e.g. gmane). Currently, if I start Gnus with M-x gnus-no-server and
DU> open news.gmane.org, it asks a password for ~/.authinfo.gpg.
I think this has to be fixed in the nntp.el code. `auth-source-search'
is called so it has to look for credentials, which means opening files.
Ted
next prev parent reply other threads:[~2011-02-23 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 18:19 Sivaram Neelakantan
2011-02-21 1:27 ` Lars Ingebrigtsen
2011-02-21 1:35 ` Lars Ingebrigtsen
2011-02-22 22:03 ` Ted Zlatanov
2011-02-23 2:14 ` Daiki Ueno
2011-02-23 2:36 ` Ted Zlatanov
2011-02-23 7:20 ` Daiki Ueno
2011-02-23 8:40 ` Lars Ingebrigtsen
2011-02-23 12:25 ` Daiki Ueno
2011-02-23 14:58 ` Ted Zlatanov
2011-02-25 4:35 ` Lars Ingebrigtsen
2011-02-25 7:17 ` Daiki Ueno
2011-02-25 14:40 ` Michael Albinus
2011-02-26 0:49 ` Daiki Ueno
2011-02-26 8:59 ` Michael Albinus
2011-02-26 9:24 ` Daiki Ueno
2011-02-25 14:43 ` Ted Zlatanov
2011-02-23 14:54 ` Ted Zlatanov [this message]
2011-02-23 8:36 ` Lars Ingebrigtsen
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=87wrkqol7y.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).