unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: emacs-devel@gnu.org
Subject: Re: epa.texi: Emacs and GnuPG pinentry
Date: Thu, 06 Jul 2023 03:15:39 +0300	[thread overview]
Message-ID: <m2wmzd28us.fsf@fastmail.fm> (raw)
In-Reply-To: <4c2b40c1-2bd6-47cb-6d66-9addd90d7518@vodafonemail.de> (Jens Schmidt's message of "Wed, 5 Jul 2023 00:13:27 +0200")

Hi Jens,

On 05/07/2023 00:13 +0200, Jens Schmidt wrote:

[...]

> What puzzled me during my first-time setup were the different modes of
> Emacs as GnuPG Pinentry.  Basically you can have for GnuPG >= 2.1:
>
> 1. Use Emacs only for GnuPG requests that are triggered by Emacs itself
>    (aka loopback pinentry),
>
> 2. use Emacs for *all* GnuPG requests (also non-Emacs ones), or
>
> 3. use Emacs for all GnuPG requests with some other non-Emacs Pinentry
>    as fallback.
>
> The latter two alternatives require pinentry.el, which was present in
> Emacs core only in versions [25, ..., 27] (see
> https://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00233.html).
> Plus they are not supported on Debian.
>
> While some users may consider alternatives 2. and 3. desirable I'm not
> sure whether I should describe their setup in detail in epa.texi.  I
> could just mention them and that "they are not recommended for use".  Or
> whatever.
>
> WDYT?

I think that putting (setq epg-pinentry-mode 'loopback) into .emacs is
all that should be needed.  BTW, we could think of making this value the
default.

Filipp



  reply	other threads:[~2023-07-06  0:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 22:13 epa.texi: Emacs and GnuPG pinentry Jens Schmidt
2023-07-06  0:15 ` Filipp Gunbin [this message]
2023-08-14 10:13 ` Björn Bidar
2023-08-14 20:10   ` Jens Schmidt

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=m2wmzd28us.fsf@fastmail.fm \
    --to=fgunbin@fastmail.fm \
    --cc=emacs-devel@gnu.org \
    --cc=jschmidt4gnu@vodafonemail.de \
    /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).