From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: bug#37025: 27.0.50; smime signing and encryption does not work any longer
Date: Thu, 15 Aug 2019 18:03:23 +0300 [thread overview]
Message-ID: <837e7eqxms.fsf@gnu.org> (raw)
In-Reply-To: <87sgq27tlb.fsf@mat.ucm.es> (message from Uwe Brauer on Thu, 15 Aug 2019 09:53:20 +0200)
> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Thu, 15 Aug 2019 09:53:20 +0200
>
> There is a ongoing discussion about a bug which was introduced in commit
> 74579d3d2bb82f300a6f2d81b7b559f0a24061db
Indeed. And there's no need to split that discussion into 2 mailing
lists. Those who are relevant to making the decision about the fix
read the bug list anyway.
> There is however a quick «fix»
>
>
> (mml-secure-smime-sign-with-sender nil)
> *did not help*, although I am using smime not opengpg.
> But
> (mml-secure-openpgp-sign-with-sender nil)
> *did help*.
>
> This should be mentioned in the documentation (NEWS and in the
> relevant doc strings)
>
> So far Teemu already sent a patch to the bugs list. It would be good if
> either this patch were applied as soon as possible or, even better, the
> patch were to be discussed, since it might causes problems with older
> openpgp versions.
Two comments (1) please wait for at least a few days before deciding
that the matter stalled and needs to be expedited, let alone in
another list; and (2) I personally didn't get the impression that the
proposed fix is final and/or agreed upon, due to the issue with the
version of gpg.
Meanwhile, you have the patch, and can apply it locally if it's urgent
for you.
next prev parent reply other threads:[~2019-08-15 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:53 bug#37025: 27.0.50; smime signing and encryption does not work any longer Uwe Brauer
2019-08-15 15:03 ` Eli Zaretskii [this message]
2019-08-18 12:29 ` Uwe Brauer
2019-08-18 14:23 ` Eli Zaretskii
2019-08-18 15:14 ` Teemu Likonen
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=837e7eqxms.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).