From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: gnus / gpg agent interaction after upgrade to Fedora 23
Date: Sun, 17 Jan 2016 23:36:06 -0500 [thread overview]
Message-ID: <84twmbec7d.fsf@davestoy.home> (raw)
In-Reply-To: <87a8o3cyzk.fsf@hope.eyrie.org> (Russ Allbery's message of "Sun, 17 Jan 2016 20:06:55 -0800")
> david.goldberg6@verizon.net (Dave Goldberg) writes:
>
>> I've read through the stuff in Bugzilla and a couple other posts. I get
>> that in Fedora 23 the Gnome password manager no longer manages gpg keys
>> and that gpg-agent is now running separately. That's OK for working
>> with gpg2 on the command line, but I can't figure out how to get it to
>> work with Gnus (latest git) and Emacs 24.5.1 as distributed with Fedora
>> 23. I've installed the pinentry-gnome3 and pinentry-emacs packages but
>> whenever Gnus needs to go to, say, .authinfo.gpg, I'm prompted for my
>> passphrase in the minibuffer which works, except that the key is
>> subsequently closed and any subsequent need to get into that file
>> results in another prompt. What am I missing?
>
> Try (setq epg-gpg-program "gpg2"). By default, I think it uses gpg, which
> is not compatible with the gpg-agent that comes with gpg2.
>
> That fixed it for me, at least.
That solves it. Thanks!
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2016-01-18 4:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 4:02 Dave Goldberg
2016-01-18 4:06 ` Russ Allbery
2016-01-18 4:36 ` Dave Goldberg [this message]
2016-02-06 5:53 ` Lars Ingebrigtsen
2016-02-06 8:24 ` Teemu Likonen
2016-02-06 18:17 ` Russ Allbery
2016-02-07 2:02 ` 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=84twmbec7d.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).