PKCS7_get0_signers(3ssl)

1PKCS7_VERIFY(3)                     OpenSSL                    PKCS7_VERIFY(3)
2
3
4

NAME

6       PKCS7_verify, PKCS7_get0_signers - verify a PKCS#7 signedData structure
7

SYNOPSIS

9        #include <openssl/pkcs7.h>
10
11        int PKCS7_verify(PKCS7 *p7, STACK_OF(X509) *certs, X509_STORE *store,
12                         BIO *indata, BIO *out, int flags);
13
14        STACK_OF(X509) *PKCS7_get0_signers(PKCS7 *p7, STACK_OF(X509) *certs, int flags);
15

DESCRIPTION

17       PKCS7_verify() verifies a PKCS#7 signedData structure. p7 is the PKCS7
18       structure to verify. certs is a set of certificates in which to search
19       for the signer's certificate. store is a trusted certificate store
20       (used for chain verification). indata is the signed data if the content
21       is not present in p7 (that is it is detached). The content is written
22       to out if it is not NULL.
23
24       flags is an optional set of flags, which can be used to modify the
25       verify operation.
26
27       PKCS7_get0_signers() retrieves the signer's certificates from p7, it
28       does not check their validity or whether any signatures are valid. The
29       certs and flags parameters have the same meanings as in PKCS7_verify().
30

VERIFY PROCESS

32       Normally the verify process proceeds as follows.
33
34       Initially some sanity checks are performed on p7. The type of p7 must
35       be signedData. There must be at least one signature on the data and if
36       the content is detached indata cannot be NULL.  If the content is not
37       detached and indata is not NULL, then the structure has both embedded
38       and external content. To treat this as an error, use the flag
39       PKCS7_NO_DUAL_CONTENT.  The default behavior allows this, for
40       compatibility with older versions of OpenSSL.
41
42       An attempt is made to locate all the signer's certificates, first
43       looking in the certs parameter (if it is not NULL) and then looking in
44       any certificates contained in the p7 structure itself. If any signer's
45       certificates cannot be located the operation fails.
46
47       Each signer's certificate is chain verified using the smimesign purpose
48       and the supplied trusted certificate store. Any internal certificates
49       in the message are used as untrusted CAs. If any chain verify fails an
50       error code is returned.
51
52       Finally the signed content is read (and written to out is it is not
53       NULL) and the signature's checked.
54
55       If all signature's verify correctly then the function is successful.
56
57       Any of the following flags (ored together) can be passed in the flags
58       parameter to change the default verify behaviour. Only the flag
59       PKCS7_NOINTERN is meaningful to PKCS7_get0_signers().
60
61       If PKCS7_NOINTERN is set the certificates in the message itself are not
62       searched when locating the signer's certificate. This means that all
63       the signers certificates must be in the certs parameter.
64
65       If the PKCS7_TEXT flag is set MIME headers for type text/plain are
66       deleted from the content. If the content is not of type text/plain then
67       an error is returned.
68
69       If PKCS7_NOVERIFY is set the signer's certificates are not chain
70       verified.
71
72       If PKCS7_NOCHAIN is set then the certificates contained in the message
73       are not used as untrusted CAs. This means that the whole verify chain
74       (apart from the signer's certificate) must be contained in the trusted
75       store.
76
77       If PKCS7_NOSIGS is set then the signatures on the data are not checked.
78

NOTES

80       One application of PKCS7_NOINTERN is to only accept messages signed by
81       a small number of certificates. The acceptable certificates would be
82       passed in the certs parameter. In this case if the signer is not one of
83       the certificates supplied in certs then the verify will fail because
84       the signer cannot be found.
85
86       Care should be taken when modifying the default verify behaviour, for
87       example setting PKCS7_NOVERIFY|PKCS7_NOSIGS will totally disable all
88       verification and any signed message will be considered valid. This
89       combination is however useful if one merely wishes to write the content
90       to out and its validity is not considered important.
91
92       Chain verification should arguably be performed  using the signing time
93       rather than the current time. However since the signing time is
94       supplied by the signer it cannot be trusted without additional evidence
95       (such as a trusted timestamp).
96

RETURN VALUES

98       PKCS7_verify() returns one for a successful verification and zero if an
99       error occurs.
100
101       PKCS7_get0_signers() returns all signers or NULL if an error occurred.
102
103       The error can be obtained from ERR_get_error(3)
104

BUGS

106       The trusted certificate store is not searched for the signers
107       certificate, this is primarily due to the inadequacies of the current
108       X509_STORE functionality.
109
110       The lack of single pass processing and need to hold all data in memory
111       as mentioned in PKCS7_sign() also applies to PKCS7_verify().
112

COPYRIGHT

117       Copyright 2002-2016 The OpenSSL Project Authors. All Rights Reserved.
118
119       Licensed under the OpenSSL license (the "License").  You may not use
120       this file except in compliance with the License.  You can obtain a copy
121       in the file LICENSE in the source distribution or at
122       <https://www.openssl.org/source/license.html>.
123
124
125
1261.1.1                             2018-09-11                   PKCS7_VERIFY(3)