From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ulrich Mueller <ulm@gentoo.org> Newsgroups: gmane.emacs.bugs Subject: bug#67012: 29.1; epa-sign-file pinentry loopback mode does not work with S/MIME Date: Sun, 19 Nov 2023 12:13:08 +0100 Message-ID: <uttpim1x7@gentoo.org> References: <u4jhvqus0@gentoo.org> <83jzqjqfma.fsf@gnu.org> <87leaz9hrv.fsf@gmx.de> <83h6lnq7y7.fsf@gnu.org> <u34x6nhuq@gentoo.org> <uy1ewmwve@gentoo.org> <8334x2mh5s.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4370"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 67012@debbugs.gnu.org, michael.albinus@gmx.de To: Eli Zaretskii <eliz@gnu.org> Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Nov 19 12:14:23 2023 Return-path: <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org> Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>) id 1r4fkt-0000yw-98 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 19 Nov 2023 12:14:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from <bug-gnu-emacs-bounces@gnu.org>) id 1r4fkZ-0002mZ-7h; Sun, 19 Nov 2023 06:14:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1r4fkX-0002lm-FI for bug-gnu-emacs@gnu.org; Sun, 19 Nov 2023 06:14:01 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1r4fkX-0007f0-3j for bug-gnu-emacs@gnu.org; Sun, 19 Nov 2023 06:14:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1r4fkX-00088N-Pa for bug-gnu-emacs@gnu.org; Sun, 19 Nov 2023 06:14:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ulrich Mueller <ulm@gentoo.org> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org> Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 19 Nov 2023 11:14:01 +0000 Resent-Message-ID: <handler.67012.B67012.170039240631202@debbugs.gnu.org> Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 67012 X-GNU-PR-Package: emacs Original-Received: via spool by 67012-submit@debbugs.gnu.org id=B67012.170039240631202 (code B ref 67012); Sun, 19 Nov 2023 11:14:01 +0000 Original-Received: (at 67012) by debbugs.gnu.org; 19 Nov 2023 11:13:26 +0000 Original-Received: from localhost ([127.0.0.1]:50104 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces@debbugs.gnu.org>) id 1r4fjx-00087C-PC for submit@debbugs.gnu.org; Sun, 19 Nov 2023 06:13:26 -0500 Original-Received: from dev.gentoo.org ([2001:470:ea4a:1:5054:ff:fec7:86e4]:54075 helo=smtp.gentoo.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <ulm@gentoo.org>) id 1r4fjs-00086t-Rt for 67012@debbugs.gnu.org; Sun, 19 Nov 2023 06:13:24 -0500 In-Reply-To: <8334x2mh5s.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 19 Nov 2023 07:43:59 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-gnu-emacs>, <mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe> List-Archive: <https://lists.gnu.org/archive/html/bug-gnu-emacs> List-Post: <mailto:bug-gnu-emacs@gnu.org> List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>, <mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe> Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:274608 Archived-At: <http://permalink.gmane.org/gmane.emacs.bugs/274608> >>>>> On Sun, 19 Nov 2023, Eli Zaretskii wrote: >> From: Ulrich Mueller <ulm@gentoo.org> >> Cc: Eli Zaretskii <eliz@gnu.org>, Michael Albinus <michael.albinus@gmx.de> >> Date: Fri, 17 Nov 2023 12:40:05 +0100 >> >> Until there's a proper fix (not anytime soon, I suppose?), could we >> please disable pinentry loopback with gpgsm? See patch below. >> >> That way, the user could still set epg-pinentry-mode to loopback for use >> with gpg2, and with gpgsm it would fall back to passphrase input through >> the pinentry program (i.e. in the GUI). This seems to be better than >> erroring out. >> >> (In fact, I use gpgsm with pinentry.el from Emacs 25.3 as a workaround. >> Unfortunately, that package has been removed as a fix for bug #27445.) > I have difficulty making a decision about this, as I don't feel I > understand the situation well enough. Can you please help me by > answering the following questions: > . are we talking about a single problem or about several ones? the > original report was about invoking gpgsm, but then you started > talking about gpg2 as well? Single problem, and it affects only gpgsm. I've mentioned gpg2 only for the reason that any fix or workaround shouldn't change existing behaviour with gpg2. (So, for example, omitting "--pinentry-mode loopback" should be conditional on the CMS protocol.) > . is this a recent regression in Emacs, or did this problem exist in > older versions of Emacs as well? or is this due to some recent > change in GnuPG? AFAICS it is an old problem, not related to any recent changes in Emacs or GnuPG. And IIUC properly fixing it would require major changes for either EasyPG or gpgsm, because the design of EasyPG relies on the status messages output by gpg2 with the --status-fd option. gpgsm doesn't output most of these messages (see the examples in message #32 above). It looks like bug #59178 is about the same issue (but that report was somewhat sidetracked). Sorry that I hadn't noticed before filing this report.