[Enigmail] S/MIME + Enigmail bug

Patrick Brunschwig patrick at enigmail.net
Wed Mar 11 10:41:53 CET 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 10.03.15 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.

Looks like I forgot that S/MIME status could change as well ...

Fixed on master.

Thanks
- -Patrick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVAA3gAAoJENsRh7ndX2k7U2UP/1B9nkiVBJQdEU3O09nU5nwc
fHw1KLdIgq0YvTC2ghw/64ShBTHbYAnSyVosxiQXCr2/BzYa2tC0wKA4xlaUsAFy
MZdA5ts1jK9UgtKD4dIUgVeyOyIKAYPRO+M5RuBlKDPIXL4/5msYcUIQ8haeoDKZ
4bJMGdqtQEdCziynvsmHqHAMcwGiKIWp8ivjby8I4Qg3rmGU7boyEngELu/AINhs
q2EZjPhrCY6SBggzzbQZwLRC2M8nCUG6krfttygc48Fv2vbn/0a02TSNHaV8sF2n
PzZu/z8rxgtec6cvcgN+Ww1JEmyNnXpTMud4SeMOys3EPPP/8sddxAX/VJKut8Me
gyuokP841MQ+a9NIq/I0k2eosOKlAotgWt1TSa3jrZplwW9q0VKPZ2qbEGqWe+Yf
NXZEo45LUHCMNGohhF9UXT0Gu1txx0LsdJ2+KRoWlC6hWmYr6n5J1fP7Hi0G7pO+
sDdaEkmW0ctoCoO7fSCVfnZXks5gLx5nGj2JXKq0zXa4h+gjo7IvWACUDldoRR6e
PeDbclZxhQocTI7M6cd9XrkWTErp61vucsD/aWEpWMFiA6yMO1Wg9gX/aCHTtdPg
EOSmCuo0q2hyy8goyx2ZII2LsOoaRZEjjk1QMllZ3j4+RzuACFyNdmVu91qwH2Hd
Eu1elJKiPKlaq03HAgVb
=WwF8
-----END PGP SIGNATURE-----



More information about the enigmail-users mailing list