From: Christoph Groth <christoph@grothesque.org>
To: ding@gnus.org
Subject: S/MIME-signed messages are sent with wrong passphrase
Date: Sat, 27 Sep 2014 12:21:23 +0200 [thread overview]
Message-ID: <87iok9pdng.fsf@grothesque.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
Hi,
I noticed that (with epg and recent Gnus) a S/MIME-signed message is
sent out even when the passphrase entry has been unsuccessful (because
pinentry’s cancel button was pressed, or because a wrong passphrase has
been entered multiple times). The sent-out message contains some
invalid signature.
OpenPGP-signed messages behave reasonably, i.e. one finds oneself in the
message buffer after a failed passphrase entry.
Any ideas where to look to fix this in S/MIME?
Christoph
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 810 bytes --]
next reply other threads:[~2014-09-27 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 10:21 Christoph Groth [this message]
2014-09-27 13:12 ` Ted Zlatanov
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=87iok9pdng.fsf@grothesque.org \
--to=christoph@grothesque.org \
--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).