#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)
--------------------------+----------------------
Reporter: michele | Owner: mutt-dev
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: mutt | Version: 1.9.2
Resolution: | Keywords:
--------------------------+----------------------
Comment (by kevin8t8):
I haven't spent much time looking at the s/mime decryption code, and was
curious why the variable is called {{{smime_default_key}}}, so I'm taking
a closer look.
It looks like {{{smime_default_key}}} '''will''' be used for decryption if
{{{smime_decrypt_use_default_key}}} is set. This was set up before I
added a capability flag to the s/mime .index files. Since the value is
overwritten by "sign (a)s", I'm not sure this is a very good idea
anymore...
So we might be able to do this for s/mime, but I have reservations given
the sign (a)s overwriting behavior. It's more certainly not a good idea
for pgp.
If I could wipe the slate clean, I would probably create a
{{{pgp_default_key}}}, along with {{{pgp_sign_key}}} and
{{{pgp_encrypt_key}}} that would override the value in
{{{pgp_default_key}}} if they were set. I might also store the value set
by "sign (a)s" in the pgp menu in a separate place, instead of overwriting
the configuration variable. Likewise for s/mime.
But given the current state, I'd rather keep the self-encrypt vars as is.
The variables won't get surprisingly overwritten, and (for pgp) we won't
suddenly start trying to encrypt using a key with no encryption
capability.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3983#comment:14>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
