unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: emacs-devel@gnu.org
Subject: Re: epa.texi: Emacs and GnuPG pinentry
Date: Mon, 14 Aug 2023 22:10:39 +0200	[thread overview]
Message-ID: <89ec500d-9141-2545-d999-f91e95b09cac@vodafonemail.de> (raw)
In-Reply-To: <87bkfa3paq.fsf@thaodan.de>

On 2023-08-14  12:13, Björn Bidar wrote:

> I'm not 100% sure but I think not all pinentry's support loopback.
> The user has to make sure that his does support it.

Hm ... that let me worry a bit, since I updated the documentation
in epa.texi some time ago already.  So I tested, all running from an
Emacs 27 -Q:

*** epg-pinentry-mode == nil

echo RELOADAGENT | gpg-connect-agent
# only pinentry executable on my system
sudo chmod a-x /usr/bin/pinentry-gnome3

(setq epg-pinentry-mode nil)

C-x C-f ~/tmp/test/xxx.pgp

=>

  Error while decrypting with "/usr/bin/gpg":

  gpg: encrypted with 3072-bit RSA key, ID D0EB77D91C0802D6, created 2022-12-03
        "test-key"
  gpg: public key decryption failed: No pinentry
  gpg: decryption failed: No secret key

So far so expected.

*** epg-pinentry-mode == 'loopback

echo RELOADAGENT | gpg-connect-agent
sudo chmod a-x /usr/bin/pinentry-gnome3

(setq epg-pinentry-mode 'loopback)

C-x C-f ~/tmp/test/xxx.pgp

=> file gets found and decrypted without problems

From that test I'd conclude that loopback pinentry works even if no
pinentry executable is available at all, so I somewhat doubt that
some pinentry executables would not support it.

Or did I misunderstand you here?  Or do you have further information?

Thanks!




      reply	other threads:[~2023-08-14 20:10 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
2023-08-14 10:13 ` Björn Bidar
2023-08-14 20:10   ` Jens Schmidt [this message]

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=89ec500d-9141-2545-d999-f91e95b09cac@vodafonemail.de \
    --to=jschmidt4gnu@vodafonemail.de \
    --cc=bjorn.bidar@thaodan.de \
    --cc=emacs-devel@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).