Commit e8d7ba81af for openssl.org

commit e8d7ba81af8bfc0212be496aa21f0e3f4b8e266b
Author: Dr. David von Oheimb <dev@ddvo.net>
Date:   Mon Aug 31 15:09:25 2026 +0200

    CMS_verify.pod,openssl-cms.pod.in: fix doc mistakes w.r.t. CMS_VERIFY_PARTIAL introduced by PR #27604

    Reviewed-by: Mounir Idrassi <mounir.idrassi@idrix.fr>
    Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com>
    Reviewed-by: Eugene Syromiatnikov <esyr@openssl.org>
    Merge-date: Thu Sep  3 09:26:57 2026
    Merged-from: https://github.com/openssl/openssl/pull/22285

diff --git a/doc/man1/openssl-cms.pod.in b/doc/man1/openssl-cms.pod.in
index ef2fc45988..3226f49f4f 100644
--- a/doc/man1/openssl-cms.pod.in
+++ b/doc/man1/openssl-cms.pod.in
@@ -498,8 +498,9 @@ as a source of candidate signers.
 With B<-nointern> these will be the only signer certificates considered.

 Note that a message can have multiple signers.
-When verifying a multi-signed message, all the signatures must be valid,
-and so all the signer certificates need to be available.
+In such cases, all signer certificates must be available.
+When verifying a multi-signed message, all the signatures must be valid
+unless B<-verify_partial> has been specified.

 The input can be in PEM, DER, or PKCS#12 format.

diff --git a/doc/man3/CMS_verify.pod b/doc/man3/CMS_verify.pod
index 303b864eca..92e1012210 100644
--- a/doc/man3/CMS_verify.pod
+++ b/doc/man3/CMS_verify.pod
@@ -90,8 +90,7 @@ First, they are searched among the certificates provided
 in the I<certs> parameter (if it is not NULL).
 Then they are looked up among the certificates contained
 in the I<cms> structure unless B<CMS_NOINTERN> is set.
-If any signer certificate cannot be located, the operation fails unless
-B<CMS_VERIFY_PARTIAL> is set, where one signer certificate can be sufficient.
+If any signer certificate cannot be located, the operation fails.
 Signer associations are retained between verification calls.

 Each found signer certificate is chain verified using I<store> as the trusted