From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: gpg 2.2 and epa
Date: Mon, 03 Dec 2018 18:17:59 +0300 [thread overview]
Message-ID: <m2ftvek5aw.fsf@fgunbin.playteam.ru> (raw)
In-Reply-To: <460fc2c7-e424-4b84-deb9-0fd169076e25@cs.ucla.edu> (Paul Eggert's message of "Sun, 2 Dec 2018 16:47:29 -0800")
On 02/12/2018 16:47 -0800, Paul Eggert wrote:
> Richard Stallman wrote:
>> I tried installing gpg 2.2 some months ago, but Emacs master ceased to
>> recognize when it was asking for a password. Has anyone had success
>> with this?
>
> Emacs master works for me on my Ubuntu 18.04.1 desktop, where "gpg --version"
> reports gpg (GnuPG) 2.2.4 with libgcrypt 1.8.1.
>
> Emacs master (like Emacs 26.1) delegates password handling to gpg2. That is,
> Emacs itself isn't responsible for reading passphrases; gpg2 does it for Emacs.
> On my desktop, when I am using Emacs and need a GPG passphrase, a window pops up
> (I assume generated by the GPG agent), and the agent remembers the key.
>
> If you want to continue to type the passphrase into Emacs, here is a relevant
> 20-message thread, dated 2016:
>
> https://lists.gnu.org/archive/html/help-gnu-emacs/2016-02/msg00102.html
>
> with the conclusion seeming to be "it's not worth the trouble".
With (setq epg-pinentry-mode 'loopback), gpg redirects passphrase
quering to Emacs. This works ok in master. No other settings should be
required for that.
Filipp
next prev parent reply other threads:[~2018-12-03 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 23:38 gpg 2.2 and epa Richard Stallman
2018-12-03 0:47 ` Paul Eggert
2018-12-03 6:05 ` Eli Zaretskii
2018-12-03 15:17 ` Filipp Gunbin [this message]
2018-12-31 16:21 ` Ted Zlatanov
2018-12-31 16:46 ` Teemu Likonen
2018-12-31 18:06 ` Ted Zlatanov
2019-01-17 19:48 ` Colin Baxter
2018-12-04 0:04 ` Richard Stallman
2018-12-03 0:54 ` Juri Linkov
2018-12-03 1:45 ` Óscar Fuentes
2018-12-04 0:05 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ftvek5aw.fsf@fgunbin.playteam.ru \
--to=fgunbin@fastmail.fm \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).