From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: S/MIME-signed messages are sent with wrong passphrase
Date: Sat, 27 Sep 2014 09:12:49 -0400 [thread overview]
Message-ID: <m2mw9lmcku.fsf@lifelogs.com> (raw)
In-Reply-To: <87iok9pdng.fsf@grothesque.org>
On Sat, 27 Sep 2014 12:21:23 +0200 Christoph Groth <christoph@grothesque.org> wrote:
CG> I noticed that (with epg and recent Gnus) a S/MIME-signed message is
CG> sent out even when the passphrase entry has been unsuccessful (because
CG> pinentry’s cancel button was pressed, or because a wrong passphrase has
CG> been entered multiple times). The sent-out message contains some
CG> invalid signature.
CG> OpenPGP-signed messages behave reasonably, i.e. one finds oneself in the
CG> message buffer after a failed passphrase entry.
CG> Any ideas where to look to fix this in S/MIME?
AFAICT this has already been reported in
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18513 and is possibly a
release blocker for the next Emacs release. If it's the same issue or a
variation thereof, please add your notes to that bug report.
Thanks
Ted
prev parent reply other threads:[~2014-09-27 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 10:21 Christoph Groth
2014-09-27 13:12 ` Ted Zlatanov [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2mw9lmcku.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).