unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 67012@debbugs.gnu.org, michael.albinus@gmx.de
Subject: bug#67012: 29.1; epa-sign-file pinentry loopback mode does not work with S/MIME
Date: Sat, 25 Nov 2023 14:27:45 +0200	[thread overview]
Message-ID: <838r6mc91a.fsf@gnu.org> (raw)
In-Reply-To: <ua5r2m6al@gentoo.org> (message from Ulrich Mueller on Sat, 25 Nov 2023 12:16:50 +0100)

> From: Ulrich Mueller <ulm@gentoo.org>
> Cc: 67012@debbugs.gnu.org,  michael.albinus@gmx.de
> Date: Sat, 25 Nov 2023 12:16:50 +0100
> 
> >>>>> On Sat, 25 Nov 2023, Eli Zaretskii wrote:
> 
> > OK, thanks.  So please install this on the master branch.
> 
> Done. I've also added a short note in doc/misc/epa.texi.
> 
> > Should we perhaps have something about this in etc/PROBLEMS?  That is,
> > after you install your changes?  If so, feel free to add there
> > whatever you think is appropriate.
> 
> This ok?

Yes.

>    *** EasyPG loopback pinentry does not work with gpgsm.
> 
>    This happens with the 'gpgsm' command from all versions of GnuPG.
>    EasyPG relies on the machine-parseable interface that is provided by
>    'gpg2' with option '--status-fd', but gpgsm does not support this.
> 
>    As a workaround, input the passphrase with a GUI-capable pinentry
>    program like 'pinentry-gnome' or 'pinentry-qt5'.  Alternatively, you
>    can use the 'pinentry' package from Emacs 25.
> 
> Add to etc/PROBLEMS in master or emacs-29 branch?

On emacs-29, I think.

Thanks.





      parent reply	other threads:[~2023-11-25 12:27 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
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 [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=838r6mc91a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67012@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=ulm@gentoo.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).