Gnus development mailing list
 help / color / mirror / Atom feed
From: Gijs Hillenius <gijs@hillenius.net>
To: ding@gnus.org
Subject: Re: auth-sources: 8 password prompts for accessing one single imap server
Date: Tue, 28 Sep 2010 09:25:34 +0200	[thread overview]
Message-ID: <87bp7il47l.fsf@hillenius.net> (raw)
In-Reply-To: <871v8eyk7a.fsf@lifelogs.com>

On 27 Sep 2010, Ted Zlatanov wrote:

> On Mon, 27 Sep 2010 22:50:57 +0200 Tassilo Horn <tassilo@member.fsf.org> wrote:
>
> TH> I use an emacs 24 bzr build from yesterday.  When I find ~/.authinfo.gpg
> TH> which is a symlink for ~/repos/configs/dot-authinfo.gpg, I have to enter
> TH> the passphrase twice.  When I kill the buffer and find ~/.authinfo.gpg
> TH> again, I still have to enter it twice again.
>
> TH> When I find the real file (not the symlink) directly, I have to give my
> TH> password only once to open that file.  But after killing the buffer and
> TH> finding the file again, I'm again queried...
>
> I looked and couldn't find the problem; epa-file.el says:
>
> 	(setq file (file-truename file))
>
> before checking or caching the passphrase so it should Just Work.  Check
> what `file-truename' says for your link but either way that seems like
> an EPA bug.  Also look at the contents of `epa-file-passphrase-alist'
> before and after the first failed passphrase entry, and after the second
> successful one.

Here, on Debian Testing/Unstable using emacs-snapshot, I don't have /
see / can't find nor get a buffer called / "epa-file-passphrase-alist".

That would explain the repeated asking for a password, would it not?

Library is file /usr/share/emacs/24.0.50/lisp/epa-file.elc







  parent reply	other threads:[~2010-09-28  7:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27  0:09 Tassilo Horn
2010-09-27  6:38 ` Vegard Vesterheim
2010-09-27  7:59   ` Drew Hess
2011-02-25 22:19     ` Ted Zlatanov
2010-09-27 16:49   ` Lars Magne Ingebrigtsen
2010-09-27 17:13     ` Vegard Vesterheim
2010-09-27 17:21       ` Lars Magne Ingebrigtsen
2010-09-27 20:50         ` Tassilo Horn
2010-09-27 20:57           ` Lars Magne Ingebrigtsen
2010-09-30  6:30             ` Tassilo Horn
2010-09-30 15:44               ` Ted Zlatanov
2010-10-05  7:16                 ` Tassilo Horn
2010-10-06  7:20                   ` "epa (Caching Passphrases)" Daiki Ueno
2010-10-06 12:22                     ` Ted Zlatanov
2010-10-06 12:38                       ` Daiki Ueno
2010-10-06 12:52                         ` Ted Zlatanov
2010-10-06 13:25                           ` Daiki Ueno
2010-10-07 19:38                             ` Lars Magne Ingebrigtsen
2010-10-08 15:38                             ` Ted Zlatanov
2010-09-27 21:01           ` auth-sources: 8 password prompts for accessing one single imap server Ted Zlatanov
2010-09-27 21:42             ` Tassilo Horn
2010-09-28  7:25             ` Gijs Hillenius [this message]
2010-09-28 10:19               ` Lars Magne Ingebrigtsen
2010-09-28 10:32                 ` Gijs Hillenius
2010-09-28 12:04                   ` Dave Goldberg
2010-09-28 13:10                     ` Gijs Hillenius
2010-09-28 13:42                       ` Gijs Hillenius
2010-09-27 16:54 ` Lars Magne Ingebrigtsen
2010-09-27 18:37   ` Ted Zlatanov
2010-09-27 18:48     ` Lars Magne Ingebrigtsen
2010-09-27 18:52       ` 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=87bp7il47l.fsf@hillenius.net \
    --to=gijs@hillenius.net \
    --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).