Discussion:
S/MIME-signed messages are sent with wrong passphrase
Christoph Groth
2014-09-27 10:21:23 UTC
Permalink
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
Ted Zlatanov
2014-09-27 13:12:49 UTC
Permalink
On Sat, 27 Sep 2014 12:21:23 +0200 Christoph Groth <***@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

Loading...