diff options
| author | Werner Koch <[email protected]> | 2023-08-31 10:02:02 +0000 |
|---|---|---|
| committer | Werner Koch <[email protected]> | 2023-08-31 10:02:02 +0000 |
| commit | d75b2a91517397261c2508dba058611f803c0733 (patch) | |
| tree | 380b1f0e36039b170deb559f18dafbde737ab60f /doc/gpgme.texi | |
| parent | qt: Allow specifying user IDs to use when refreshing keys via WKD (diff) | |
| download | gpgme-d75b2a91517397261c2508dba058611f803c0733.tar.gz gpgme-d75b2a91517397261c2508dba058611f803c0733.zip | |
Support GPGME_ENCRYPT_ALWAYS_TRUST also for S/MIME.
* src/engine-gpgsm.c (gpgsm_encrypt): Send the always-trust options.
* tests/run-encrypt.c: Add option --always-trust.
--
Note that the run-encrypt test tool used to assume always-trust for
OpenPGP since 1.7.0 This bug has also been fixed by introducing the
explicit option.
GnuPG-bug-id: 6559
Diffstat (limited to 'doc/gpgme.texi')
| -rw-r--r-- | doc/gpgme.texi | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/gpgme.texi b/doc/gpgme.texi index 8fc6a263..714ff916 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -6546,6 +6546,10 @@ recipients in @var{recp} should be trusted, even if the keys do not have a high enough validity in the keyring. This flag should be used with care; in general it is not a good idea to use any untrusted keys. +For the S/MIME (CMS) protocol this flag allows to encrypt to a +certificate without running any checks on the validity of the +certificate. + @item GPGME_ENCRYPT_NO_ENCRYPT_TO @since{1.2.0} |