Open Bug 1796634 Opened 2 years ago Updated 2 years ago

Decide about defaults for encryption automatism (the automatism is limited to scenarios in which no further user configuration is necessary)

Categories

(MailNews Core :: Security: OpenPGP, enhancement)

Product:
MailNews Core
Component:
Security: OpenPGP
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: KaiE, Unassigned)

References

Details

Please read bug 135636 comment 232.
This bug here is about making a decision whether we should enable automatisms by default.

This is NOT about opportunistic encryption.

Bug 135636 may introduce the ability to automatically enable encryption, if encryption is possible based on existing configuration.

The question is, should that automatism be disabled by default (user must manually change encryption setting), or should that automatism be used by default (enable or disable encryption, without having to click buttons).

I think in can be enabled by default. If users are absolutely not interested in encryption they probably never encounter the situation that the automatism kicks in, right? If they do, they can disable the automatism.

Generally I'm for data security. Encrypt e-mails whenever possible, it makes the internet a safer place. And modern messenger systems also have end-to-end encryption, so why not e-mails?

You need to log in before you can comment on or make changes to this bug.