Bugzilla

When adding suport for OpenPGP, we'll have the following categories of preferences related to the encryption technologies:

(a) General for Encryption / Signing
(b) specific to OpenPGP
(c) specific to S/MIME

It might be overkill to have three separate sub-categories.

For comparison, today, with Enigmail installed, we have the separate categories:
- security
- openpgp security

Also considering comments from bug 1532575, following is my suggestion:

Have only one sub-category for account prefs, and rename it to "Encryption & Signatures".

Inside, have three tabs at the top, label them as:
- General
- OpenPGP
- S/MIME

(Note that we'll want to continue to support both OpenPGP and S/MIME. A single account could be configured for both technologies. IMHO the user should be able to change the a default technology, both in prefs, and for an individual message.)

There are some prefs that will be shared by both, and which should live in the General tab:
- the preferred technology for new composer windows, either s/mime or openpgp
- (potentially for later, we might have an option that allows to automatically select the other technology, if the selected one cannot be used, but the other can be used)
- if saved draft messages are encrypted
- checkbox "sign by default"
- a radio button for "don't encrypt by default" or "enable encryption by default for new messages"

The suggestion is to use a radio button, not a checkbox, because:
- that's what we have today
- we consider to have a third option at a later time, which says: "encrypt new messages only if possible". This will be more work from a UI and automatic behavior point of view, so I'd like to work on that later.


Inside the S/MIME tab we'd have:
- "my certificate" for this account, selection
- a radio button with the choices:
  "use a single cert for both encryption and signing"
  or
  "peers should use a different certificate for sending me S/MIME encrypted email"
(trying to incorporate suggestions from bug 1532575.)


For the OpenPGP tab, here are several potential candidates:
- selected openpgp key id
- attach my openpgp public key to outgoing messages
- when sending an encrypted message, also protect the subject
- potentially later, a pref to control PGP/INLINE for signed only, simple plain text messages (bug 1602481)
- potentially later, whether we want to allow processing/sending of some autocrypt headers (TBD)

When adding suport for OpenPGP, we'll have the following categories of preferences related to the encryption technologies:

(a) General for Encryption / Signing
(b) specific to OpenPGP
(c) specific to S/MIME

It might be overkill to have three separate sub-categories.

For comparison, today, with Enigmail installed, we have the separate categories:
- security
- openpgp security

Also considering comments from bug 1532575, following is my suggestion:

Have only one sub-category for account prefs, and rename it to "Encryption & Signatures".

Inside, have three tabs at the top, label them as:
- General
- OpenPGP
- S/MIME

(Note that we'll want to continue to support both OpenPGP and S/MIME. A single account could be configured for both technologies. IMHO the user should be able to change the a default technology, both in prefs, and for an individual message.)

There are some prefs that will be shared by both, and which should live in the General tab:
- the preferred technology for new composer windows, either s/mime or openpgp
- (potentially for later, we might have an option that allows to automatically select the other technology, if the selected one cannot be used, but the other can be used)
- if saved draft messages are encrypted
- checkbox "sign by default"
- a radio button for "don't encrypt by default" or "enable encryption by default for new messages"

The suggestion is to use a radio button, not a checkbox, because:
- that's what we have today
- we consider to have a third option at a later time, which says: "encrypt new messages only if possible". This will be more work from a UI and automatic behavior point of view, so I'd like to work on that later.


Inside the S/MIME tab we'd have:
- "my certificate" for this account, selection
- a radio button with the choices:
  "use a single cert for both encryption and signing"
  or
  "peers should use a different certificate for sending me S/MIME encrypted email"
(trying to incorporate suggestions from bug 1532575.)


For the OpenPGP tab, here are several potential candidates:
- selected openpgp key id
- attach my openpgp public key to outgoing messages
- when sending an encrypted message, also protect the subject
- potentially later, a pref to control PGP/INLINE for signed only, simple plain text messages (bug 1602481)