From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: auth-source (.authinfo.gpg) stopped working?
Date: Mon, 27 Dec 2010 10:48:13 -0500 [thread overview]
Message-ID: <8462ufjjya.fsf@davestoy.home> (raw)
In-Reply-To: <87vd2f2w2f.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 27 Dec 2010 07:18:32 -0600")
> On Thu, 23 Dec 2010 23:45:50 -0500 david.goldberg6@verizon.net (Dave
> Goldberg) wrote:
DG> I updated this morning after staying on a version from much
DG> earlier in the month as I've been trying to debug an issue with my
DG> exchange server.
DG> Normally on running gnus, I am prompted for the passphrase for
DG> .authinfo.gpg. Assuming I don't mistype, the file is opened (by
DG> virtue of epg) and parsed and I am not prompted for any further login
DG> information.
DG> That didn't work after updating this morning. Instead I was prompted
DG> for login information even after successfully opening .authinfo.gpg.
DG> I seem to recall some discussion about the line format in there so I
DG> figured I'd go through the prompts and let it write whatever it wanted
DG> back into the file. Well nothing new got written but my connections
DG> to the servers failed. Today was surprisingly busy (had to meet a
DG> deadline before the holiday) so I reverted to my previous
DG> installation. I plan to take up debugging it next week, but if anyone
DG> has any idea what to look for I would greatly appreciate any pointers.
DG> In case it matters (as I fear it might) I am running on XEmacs 21.4.22.
> Open the .gpg file directly in Emacs. Does that work? If yes, we'll
> look for a problem in auth-source.el. If not, the problem is in EPA or
> in the GPG setup. The sequence you're describing (nothing works, you're
> prompted to save login info) suggests the latter.
Yes, opening the .gpg file works just fine. And as noted, an earlier checkout of gnus does as well. I can't check it further today, unfortunately. Weather has me working from home and I left the office machine off over the weekend so I can't access the affected copy, nor can I directly access my IMAP servers from home.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2010-12-27 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 4:45 Dave Goldberg
2010-12-27 13:18 ` Ted Zlatanov
2010-12-27 15:48 ` Dave Goldberg [this message]
2010-12-28 14:48 ` Dave Goldberg
2011-01-02 5:55 ` Lars Magne Ingebrigtsen
2011-01-03 13:35 ` Dave Goldberg
2011-01-03 14:02 ` Dave Goldberg
2011-01-03 23:59 ` Lars Magne Ingebrigtsen
2011-01-04 1:24 ` Dave Goldberg
2011-01-04 1:36 ` Daiki Ueno
2011-01-05 2:51 ` Daiki Ueno
2011-01-05 14:08 ` Dave Goldberg
2011-01-05 14:14 ` Katsumi Yamaoka
2011-01-05 18:43 ` Daiki Ueno
2011-01-06 13:12 ` Dave Goldberg
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=8462ufjjya.fsf@davestoy.home \
--to=david.goldberg6@verizon.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).