Your message dated Wed, 27 Jun 2012 07:03:00 +0200
with message-id <[email protected]>
and subject line Bug#508766: unreproducable
has caused the Debian Bug report #508766,
regarding enigmail tries to sign drafts; it should only sign messages to be
sent.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
508766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508766
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: enigmail
Version: 2:0.95.0+1-4
Try the following:
* launch an icedove process an start composing a new e-mail from an
identity configured to automatically sign messages.
* write the first half of a message, and then wait for the automatic
"save to draft" timeout to trigger.
Icedove/enigmail tries to sign the draft before storing it. This is
incorrect, because a draft is not the completed message. Should the
draft folder be shared, compromised, or otherwise publically visible,
the half-written message will be visibly and non-repudiably signed,
which is probably not the intent of the author. Depending on the
message (and the frequency of the "save to draft" automatic operation),
this could have bad consequences..
Interestingly, unless the autosave triggers first, explicitly choosing
"save draft" from the toolbar, menu, or keyboard shortcuts does *not*
have the same behavior for me. But please test for independent
verification of this slight mitigation.
I tested this with icedove 2.0.0.17-1 on an i386 platform with linux
kernel 2.6.26.
Thanks for maintaining enigmail in debian!
--dkg
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 2:1.4.1-2
Closing this bug as the last post claims that the bug is no longer
reproducible in current Ubuntu version, and the commenter did thoroughly
test it (thanks Daniel Hahler)
WM
--- End Message ---
