From d75b2a91517397261c2508dba058611f803c0733 Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Thu, 31 Aug 2023 12:02:02 +0200 Subject: 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 --- doc/gpgme.texi | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'doc') 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} -- cgit v1.2.3