Thomas Roessler wrote: > You could set (and store across postpone / resume) a flag in > msg->security that indicates that the user mangled with the encryption > settings, which would then override opportunistic encryption in the > future, for this message.
Thinking about a msg->security flag gives me another idea. How about if the opportunistic_encrypt itself is controlled by a msg->security flag? The crypt_opportunistic_encrypt configuration variable, if set, simply turns on the msg->security flag by default. Once in the compose menu, the Security: line could indicate if the opportunitic_encrypt is enabled, and there would be a toggle command to enable/disable it (regardless of whether crypt_opportunistic_encrypt is set or not). One question is whether we would allow the user to change the encryption flag if the opportunistic_encrypt flag is set, or whether they would have to toggle off opportunistic_encrypt first. -Kevin
signature.asc
Description: Digital signature
