| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137 |
- .\" -*- mode: troff; coding: utf-8 -*-
- .\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
- .\"
- .\" Standard preamble:
- .\" ========================================================================
- .de Sp \" Vertical space (when we can't use .PP)
- .if t .sp .5v
- .if n .sp
- ..
- .de Vb \" Begin verbatim text
- .ft CW
- .nf
- .ne \\$1
- ..
- .de Ve \" End verbatim text
- .ft R
- .fi
- ..
- .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
- .ie n \{\
- . ds C` ""
- . ds C' ""
- 'br\}
- .el\{\
- . ds C`
- . ds C'
- 'br\}
- .\"
- .\" Escape single quotes in literal strings from groff's Unicode transform.
- .ie \n(.g .ds Aq \(aq
- .el .ds Aq '
- .\"
- .\" If the F register is >0, we'll generate index entries on stderr for
- .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
- .\" entries marked with X<> in POD. Of course, you'll have to process the
- .\" output yourself in some meaningful fashion.
- .\"
- .\" Avoid warning from groff about undefined register 'F'.
- .de IX
- ..
- .nr rF 0
- .if \n(.g .if rF .nr rF 1
- .if (\n(rF:(\n(.g==0)) \{\
- . if \nF \{\
- . de IX
- . tm Index:\\$1\t\\n%\t"\\$2"
- ..
- . if !\nF==2 \{\
- . nr % 0
- . nr F 2
- . \}
- . \}
- .\}
- .rr rF
- .\" ========================================================================
- .\"
- .IX Title "CMS_ADD0_CERT 3ossl"
- .TH CMS_ADD0_CERT 3ossl 2025-01-17 3.4.0 OpenSSL
- .\" For nroff, turn off justification. Always turn off hyphenation; it makes
- .\" way too many mistakes in technical documents.
- .if n .ad l
- .nh
- .SH NAME
- CMS_add0_cert, CMS_add1_cert, CMS_get1_certs,
- CMS_add0_crl, CMS_add1_crl, CMS_get1_crls
- \&\- CMS certificate and CRL utility functions
- .SH SYNOPSIS
- .IX Header "SYNOPSIS"
- .Vb 1
- \& #include <openssl/cms.h>
- \&
- \& int CMS_add0_cert(CMS_ContentInfo *cms, X509 *cert);
- \& int CMS_add1_cert(CMS_ContentInfo *cms, X509 *cert);
- \& STACK_OF(X509) *CMS_get1_certs(CMS_ContentInfo *cms);
- \&
- \& int CMS_add0_crl(CMS_ContentInfo *cms, X509_CRL *crl);
- \& int CMS_add1_crl(CMS_ContentInfo *cms, X509_CRL *crl);
- \& STACK_OF(X509_CRL) *CMS_get1_crls(CMS_ContentInfo *cms);
- .Ve
- .SH DESCRIPTION
- .IX Header "DESCRIPTION"
- \&\fBCMS_add0_cert()\fR and \fBCMS_add1_cert()\fR add certificate \fIcert\fR to \fIcms\fR
- unless it is already present.
- This is used by \fBCMS_sign_ex\fR\|(3) and \fBCMS_sign\fR\|(3) and may be used before
- calling \fBCMS_verify\fR\|(3) to help chain building in certificate validation.
- As the 0 implies, \fBCMS_add0_cert()\fR adds \fIcert\fR internally to \fIcms\fR
- and on success it must not be freed up by the caller.
- In contrast, the caller of \fBCMS_add1_cert()\fR must free \fIcert\fR.
- \&\fIcms\fR must be of type signed data or (authenticated) enveloped data.
- For signed data, such a certificate can be used when signing or verifying
- to fill in the signer certificate or to provide an extra CA certificate
- that may be needed for chain building in certificate validation.
- .PP
- \&\fBCMS_get1_certs()\fR returns all certificates in \fIcms\fR.
- .PP
- \&\fBCMS_add0_crl()\fR and \fBCMS_add1_crl()\fR add CRL \fIcrl\fR to \fIcms\fR.
- \&\fIcms\fR must be of type signed data or (authenticated) enveloped data.
- For signed data, such a CRL may be used in certificate validation
- with \fBCMS_verify\fR\|(3).
- It may be given both for inclusion when signing a CMS message
- and when verifying a signed CMS message.
- .PP
- \&\fBCMS_get1_crls()\fR returns all CRLs in \fIcms\fR.
- .SH NOTES
- .IX Header "NOTES"
- The CMS_ContentInfo structure \fIcms\fR must be of type signed data or enveloped
- data or authenticated enveloped data or an error will be returned.
- .PP
- For signed data, certificates and CRLs are added to the \fIcertificates\fR and
- \&\fIcrls\fR fields of SignedData structure.
- For enveloped data they are added to \fBOriginatorInfo\fR.
- .SH "RETURN VALUES"
- .IX Header "RETURN VALUES"
- \&\fBCMS_add0_cert()\fR, \fBCMS_add1_cert()\fR and \fBCMS_add0_crl()\fR and \fBCMS_add1_crl()\fR return
- 1 for success and 0 for failure.
- .PP
- \&\fBCMS_get1_certs()\fR and \fBCMS_get1_crls()\fR return the STACK of certificates or CRLs,
- which is empty if there are none. They return NULL on error.
- Besides out-of-memory, the only error which will occur
- in practice is if the \fIcms\fR type is invalid.
- .SH "SEE ALSO"
- .IX Header "SEE ALSO"
- \&\fBERR_get_error\fR\|(3),
- \&\fBCMS_sign\fR\|(3), \fBCMS_sign_ex\fR\|(3), \fBCMS_verify\fR\|(3),
- \&\fBCMS_encrypt\fR\|(3)
- .SH HISTORY
- .IX Header "HISTORY"
- \&\fBCMS_add0_cert()\fR and \fBCMS_add1_cert()\fR have been changed in OpenSSL 3.2
- not to throw an error if a certificate to be added is already present.
- .SH COPYRIGHT
- .IX Header "COPYRIGHT"
- Copyright 2008\-2024 The OpenSSL Project Authors. All Rights Reserved.
- .PP
- Licensed under the Apache License 2.0 (the "License"). You may not use
- this file except in compliance with the License. You can obtain a copy
- in the file LICENSE in the source distribution or at
- <https://www.openssl.org/source/license.html>.
|