- ** Setting this variable will cause Mutt-ng to always attempt to
- ** cryptographically sign outgoing messages. This can be overridden
- ** by use of the \fIpgp-menu\fP, when signing is not required or
- ** encryption is requested as well. If ``$$smime_is_default'' is set,
- ** then OpenSSL is used instead to create S/MIME messages and settings can
- ** be overridden by use of the \fIsmime-menu\fP.
- ** (Crypto only)
- */
- {"pgp_autoencrypt", DT_SYN, R_NONE, UL "crypt_autoencrypt", 0},
- {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0},
- /*
- ** .pp
- ** Setting this variable will cause Mutt-ng to always attempt to PGP
- ** encrypt outgoing messages. This is probably only useful in
- ** connection to the \fIsend-hook\fP command. It can be overridden
- ** by use of the \fIpgp-menu\fP, when encryption is not required or
- ** signing is requested as well. IF ``$$smime_is_default'' is set,
- ** then OpenSSL is used instead to create S/MIME messages and
- ** settings can be overridden by use of the \fIsmime-menu\fP.
- ** (Crypto only)
- */
- {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1},
- /*
- ** .pp
- ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
- ** the principal key will inherit the subkeys' capabilities. Unset this
- ** if you want to play interesting key selection games.
- ** (PGP only)
- */
- {"pgp_replyencrypt", DT_SYN, R_NONE, UL "crypt_replyencrypt", 1},
- {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1},
- /*
- ** .pp
- ** If set, automatically PGP or OpenSSL encrypt replies to messages which are
- ** encrypted.
- ** (Crypto only)
- */
- {"pgp_replysign", DT_SYN, R_NONE, UL "crypt_replysign", 0},
- {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0},
- /*
- ** .pp
- ** If set, automatically PGP or OpenSSL sign replies to messages which are
- ** signed.
- ** .pp
- ** \fBNote:\fP this does not work on messages that are encrypted
- ** \fBand\fP signed!
- ** (Crypto only)
- */
- {"pgp_replysignencrypted", DT_SYN, R_NONE, UL "crypt_replysignencrypted",
- 0},
- {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED,
- 0},
- /*
- ** .pp
- ** If set, automatically PGP or OpenSSL sign replies to messages
- ** which are encrypted. This makes sense in combination with
- ** ``$$crypt_replyencrypt'', because it allows you to sign all
- ** messages which are automatically encrypted. This works around
- ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able
- ** to find out whether an encrypted message is also signed.
- ** (Crypto only)
- */
- {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1},
- /*
- ** .pp
- ** If set, Mutt-ng will include a time stamp in the lines surrounding
- ** PGP or S/MIME output, so spoofing such lines is more difficult.
- ** If you are using colors to mark these lines, and rely on these,
- ** you may unset this setting.
- ** (Crypto only)
- */
- {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0},
- /*
- ** .pp
- ** If set, Mutt-ng will use a possibly-running gpg-agent process.
- ** (PGP only)
- */
- {"pgp_verify_sig", DT_SYN, R_NONE, UL "crypt_verify_sig", 0},
- {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES},
- /*
- ** .pp
- ** If ``yes'', always attempt to verify PGP or S/MIME signatures.
- ** If ``ask'', ask whether or not to verify the signature.
- ** If ``no'', never attempt to verify cryptographic signatures.
- ** (Crypto only)
- */
- {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0},
- /*
- ** .pp
- ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
- ** operations. To override and to use OpenSSL instead this must be set.
- ** However, this has no effect while replying, since Mutt-ng will automatically
- ** select the same application that was used to sign/encrypt the original
- ** message. (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
- ** (S/MIME only)
- */
- {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1},
- /*
- ** .pp
- ** This flag controls whether you want to be asked to enter a label
- ** for a certificate about to be added to the database or not. It is
- ** set by default.
- ** (S/MIME only)
- */
- {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY,
- 1},
- /*
- ** .pp
- ** If set (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
- ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address
- ** to determine the key to use. It will ask you to supply a key, if it can't find one.
- ** (S/MIME only)
- */
- {"pgp_entry_format", DT_STR, R_NONE, UL & PgpEntryFormat,
- UL "%4n %t%f %4l/0x%k %-4a %2c %u"},
- /*
- ** .pp
- ** This variable allows you to customize the PGP key selection menu to
- ** your personal taste. This string is similar to ``$$index_format'', but
- ** has its own set of printf()-like sequences:
- ** .pp
- ** .dl
- ** .dt %n .dd number
- ** .dt %k .dd key id
- ** .dt %u .dd user id
- ** .dt %a .dd algorithm
- ** .dt %l .dd key length
- ** .dt %f .dd flags
- ** .dt %c .dd capabilities
- ** .dt %t .dd trust/validity of the key-uid association
- ** .dt %[<s>] .dd date of the key where <s> is an strftime(3) expression
- ** .de
- ** .pp
- ** (PGP only)
- */
- {"pgp_good_sign", DT_RX, R_NONE, UL & PgpGoodSign, 0},
- /*
- ** .pp
- ** If you assign a text to this variable, then a PGP signature is only
- ** considered verified if the output from $$pgp_verify_command contains
- ** the text. Use this variable if the exit code from the command is 0
- ** even for bad signatures.
- ** (PGP only)
- */
- {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1},
- /*
- ** .pp
- ** If set, Mutt-ng will check the exit code of the PGP subprocess when
- ** signing or encrypting. A non-zero exit code means that the
- ** subprocess failed.
- ** (PGP only)
- */
- {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0},
- /*
- ** .pp
- ** If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs.
- ** (PGP only)
- */
- {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0},
- /*
- ** .pp
- ** If set, signed and encrypted messages will consist of nested
- ** multipart/signed and multipart/encrypted body parts.