From: GH <project@gnuhacker.org>
To: Angel de Vicente <angel.vicente.garrido@gmail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: Signing a message with S/MIME in Gnus?
Date: Thu, 03 Nov 2022 18:52:40 +0100 [thread overview]
Message-ID: <87sfj0sz6f.fsf@gnuhacker.org> (raw)
In-Reply-To: <87tu3gxdkj.fsf@gmail.com> (Angel de Vicente's message of "Thu, 03 Nov 2022 15:28:12 +0000")
Angel de Vicente <angel.vicente.garrido@gmail.com> writes:
> It is very weird, maybe a bug, because I have set epg-pinentry-mode to
> loopback, which is supposed to use the Emacs minibuffer to ask for the
> passphrase of private keys. This works perfect for PGP but it throws
> an error for SMIME "Signing failed (unknown reason)". [If I set
> epg-pinentry-mode to 'nil, then I am asked for the passphrase by
> gnome-keyring and all is good (but I need to use the mini-buffer,
> since I use this machine mostly remotely].
> I chased the error down to the function "epg-sign-string" in epg.el,
> but my ELisp is very rusty and not making much progress in debugging
> the issue. I guess at some point epg.el is calling pinentry, but don't
> know how to efficiently debug this.
revert changes in epg.el and try it:
In your emacs conf:
(setq epg-pinentry-mode 'loopback)
in ~/.gnupg/gpg.conf
use-agent
pinentry-mode loopback
in ~/.gnupg/gpg-agent.conf
allow-emacs-pinentry
allow-loopback-pinentry
next prev parent reply other threads:[~2022-11-03 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 9:29 Angel de Vicente
2022-11-02 19:09 ` Jens Lechtenboerger
2022-11-02 20:51 ` Angel de Vicente
2022-11-03 7:09 ` Jens Lechtenboerger
2022-11-03 7:21 ` Angel de Vicente
2022-11-03 15:28 ` Angel de Vicente
2022-11-03 17:52 ` GH [this message]
2022-11-03 18:32 ` Angel de Vicente
2022-11-04 18:11 ` Angel de Vicente
2022-11-03 18:55 ` Jens Lechtenboerger
2022-11-03 19:25 ` Emanuel Berg
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=87sfj0sz6f.fsf@gnuhacker.org \
--to=project@gnuhacker.org \
--cc=angel.vicente.garrido@gmail.com \
--cc=info-gnus-english@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.
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).