[RFE] Option for encrypting with SMIME "if possible"

RESOLVED DUPLICATE of bug 135636

Status

Thunderbird
Security
--
enhancement
RESOLVED DUPLICATE of bug 135636
4 years ago
4 years ago

People

(Reporter: Clemens, Unassigned)

Tracking

24 Branch
x86
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140506152807

Steps to reproduce:

I installed a SMIME certificate and since I don't want to turn on encryption every time I write an email, I chose "encryption required"


Actual results:

If I want to write an unencrypted email, I always have to confirm a dialog, saying that my email will not be encrypted


Expected results:

I would like to have an option to encrypt "if possible". It's desperately annoying to choose encryption every time I write an email. And it's not better, if I have to comfirm to send unencrypted messages all the time.

I know that there is an Add-On for that problem, but in security issues I don't want to rely on thirdparty apps. I think such an option would make Thunderbird much more user-friendly and easier to use encryption!
(Reporter)

Updated

4 years ago
Severity: normal → enhancement
(Reporter)

Comment 1

4 years ago
Ok, sorry. I just saw that this topic has been discussed before, but I can't find a possibility to delete my request. 

Nevertheless I want to emphasize how important I think this option would be. 

I know that many people see security issues in this kind of setting, but I think that it's the main reason for people not using encryption. Maybe it wouldn't be the highest security level, but I think spreading encryption would be worth it.

And since there is a work-around with add-ons, it would enhance the security of those people using them.

And by the way: I can't even imagine anyone could be fine with confirming a warning-window every time trying to send an email!

Comment 2

4 years ago
Duping to bug 135636.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 135636
You need to log in before you can comment on or make changes to this bug.