From: Ulrich Mueller <ulm@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67012@debbugs.gnu.org
Subject: bug#67012: 29.1; epa-sign-file pinentry loopback mode does not work with S/MIME
Date: Thu, 09 Nov 2023 12:43:16 +0100 [thread overview]
Message-ID: <umsvnp2y3@gentoo.org> (raw)
In-Reply-To: <83v8abyxxf.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 Nov 2023 13:21:32 +0200")
>>>>> On Thu, 09 Nov 2023, Eli Zaretskii wrote:
> Isn't this one more manifestation of the GnuPG 2.4.1? See the entry
> in etc/PROBLEMS whose heading is "Saving a file encrypted with GnuPG
> via EasyPG hangs".
AFAICS this is a different problem.
> IOW, if you downgrade to an older version of GnuPG, do both problems
> go away?
My original report was with gnupg-2.4.3. I've tried again after
downgrading to gnupg-2.2.41, but the behaviour is basically the same.
The only difference is an additional line in the error message:
Error while signing with "/usr/bin/gpgsm":
gpgsm: DBG: adding certificates at level -2
gpgsm: ignoring gpg-agent inquiry 'PASSPHRASE'
gpgsm: error creating signature: No passphrase given <GPG Agent>
I see no change either when I add --passphrase-fd 0 to the args in
epg--start. That is, gpgsm still hangs as reported above.
next prev parent reply other threads:[~2023-11-09 11:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 6:56 bug#67012: 29.1; epa-sign-file pinentry loopback mode does not work with S/MIME Ulrich Mueller
[not found] ` <handler.67012.B.169951307615474.ack@debbugs.gnu.org>
2023-11-09 9:46 ` Ulrich Mueller
2023-11-09 11:21 ` Eli Zaretskii
2023-11-09 11:43 ` Ulrich Mueller [this message]
2023-11-15 14:02 ` Eli Zaretskii
2023-11-15 15:07 ` Michael Albinus
2023-11-15 15:32 ` Michael Albinus
2023-11-15 16:48 ` Eli Zaretskii
2023-11-15 17:13 ` Michael Albinus
2023-11-16 9:54 ` Ulrich Mueller
2023-11-17 11:40 ` Ulrich Mueller
2023-11-19 5:43 ` Eli Zaretskii
2023-11-19 11:13 ` Ulrich Mueller
2023-11-25 9:53 ` Eli Zaretskii
2023-11-25 11:16 ` Ulrich Mueller
2023-11-25 11:40 ` Michael Albinus
2023-11-25 12:17 ` Ulrich Mueller
2023-11-25 14:59 ` Ulrich Mueller
2023-11-25 15:44 ` Michael Albinus
2023-11-25 16:32 ` Ulrich Mueller
2023-11-25 12:27 ` Eli Zaretskii
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=umsvnp2y3@gentoo.org \
--to=ulm@gentoo.org \
--cc=67012@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.