[Enigmail] S/MIME + Enigmail bug
o.e.ekker at gmail.com
Tue Mar 10 19:52:53 CET 2015
On 10-3-2015 18:26, Robert J. Hansen wrote:
> 1. Set a default S/MIME certificate and configure Thunderbird to always
> sign messages from that account.
> 2. Compose a new message.
> 3. Click the Enigmail Sign button. A warning will appear about a
> possible conflict.
> 4. Disable S/MIME signing via the S/MIME padlock button.
> 5. Usability bug: The conflict warning does not go away.
> 6. Disable Enigmail signing.
> 7. Re-enable Enigmail signing. No conflict message is generated.
> 8. Enable S/MIME signing via the S/MIME padlock button.
> 9. Usability bug: no conflict message is shown.
I think it would be nice if Enigmail removed the original S/MIME menu
and button and put an entry for it in it's own protocol section. That
way it could ensure that always one protocol is selected: S/MIME, Inline
PGP, PGP/MIME, Unencrypted...
More information about the enigmail-users