Closed Bug 1018203 Opened 11 years ago Closed 11 years ago

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

Categories

(Thunderbird :: Security, enhancement)

24 Branch
x86
macOS
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 135636

People

(Reporter: clemens.mast, Unassigned)

Details

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!
Severity: normal → enhancement
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!
Duping to bug 135636.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.