xref: /freebsd/secure/lib/libcrypto/man/man7/x509.7 (revision 681ce946f33e75c590e97c53076e86dff1fe8f4a)
Automatically generated by Pod::Man 4.14 (Pod::Simple 3.43)

Standard preamble:
========================================================================
..
..
.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

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'.
.. .nr rF 0 . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF
Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "X509 7"
X509 7 "2021-12-14" "1.1.1m" "OpenSSL"
For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
"NAME"
x509 - X.509 certificate handling
"SYNOPSIS"
Header "SYNOPSIS" .Vb 1 #include <openssl/x509.h> .Ve
"DESCRIPTION"
Header "DESCRIPTION" An X.509 certificate is a structured grouping of information about an individual, a device, or anything one can imagine. An X.509 \s-1CRL\s0 (certificate revocation list) is a tool to help determine if a certificate is still valid. The exact definition of those can be found in the X.509 document from ITU-T, or in \s-1RFC3280\s0 from \s-1PKIX.\s0 In OpenSSL, the type X509 is used to express such a certificate, and the type X509_CRL is used to express a \s-1CRL.\s0

A related structure is a certificate request, defined in PKCS#10 from \s-1RSA\s0 Security, Inc, also reflected in \s-1RFC2896.\s0 In OpenSSL, the type X509_REQ is used to express such a certificate request.

To handle some complex parts of a certificate, there are the types X509_NAME (to express a certificate name), X509_ATTRIBUTE (to express a certificate attribute), X509_EXTENSION (to express a certificate extension) and a few more.

Finally, there's the supertype X509_INFO, which can contain a \s-1CRL,\s0 a certificate and a corresponding private key.

\fBX509_\s-1XXX\s0, d2i_X509_\s-1XXX\s0, and i2d_X509_\s-1XXX\s0 functions handle X.509 certificates, with some exceptions, shown below.

\fBX509_CRL_\s-1XXX\s0, d2i_X509_CRL_\s-1XXX\s0, and i2d_X509_CRL_\s-1XXX\s0 functions handle X.509 CRLs.

\fBX509_REQ_\s-1XXX\s0, d2i_X509_REQ_\s-1XXX\s0, and i2d_X509_REQ_\s-1XXX\s0 functions handle PKCS#10 certificate requests.

\fBX509_NAME_\s-1XXX\s0 functions handle certificate names.

\fBX509_ATTRIBUTE_\s-1XXX\s0 functions handle certificate attributes.

\fBX509_EXTENSION_\s-1XXX\s0 functions handle certificate extensions.

"SEE ALSO"
Header "SEE ALSO" \fBX509_NAME_ENTRY_get_object\|(3), \fBX509_NAME_add_entry_by_txt\|(3), \fBX509_NAME_add_entry_by_NID\|(3), \fBX509_NAME_print_ex\|(3), \fBX509_NAME_new\|(3), \fBd2i_X509\|(3), \fBd2i_X509_ALGOR\|(3), \fBd2i_X509_CRL\|(3), \fBd2i_X509_NAME\|(3), \fBd2i_X509_REQ\|(3), \fBd2i_X509_SIG\|(3), \fBX509v3\|(3), \fBcrypto\|(7)
"COPYRIGHT"
Header "COPYRIGHT" Copyright 2003-2021 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use this file except in compliance with the License. You can obtain a copy in the file \s-1LICENSE\s0 in the source distribution or at <https://www.openssl.org/source/license.html>.