$NetBSD: x509.7,v 1.8 2024/09/08 13:08:39 christos Exp $

-*- mode: troff; coding: utf-8 -*-
Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)

Standard preamble:
========================================================================
..

..

.. \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
. ds C` "" . ds C' "" 'br\} . 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 ========================================================================

Title "X509 7" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
x509 - X.509 certificate handling Header "SYNOPSIS" .Vb 1 #include <openssl/x509.h> .Ve 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 CRL (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 RFC3280 from PKIX. In OpenSSL, the type X509 is used to express such a certificate, and the type X509_CRL is used to express a CRL.

A related structure is a certificate request, defined in PKCS#10 from RSA Security, Inc, also reflected in RFC2896. 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 CRL, a certificate and a corresponding private key.

\fBX509_XXX, d2i_X509_XXX, and i2d_X509_XXX functions handle X.509 certificates, with some exceptions, shown below.

\fBX509_CRL_XXX, d2i_X509_CRL_XXX, and i2d_X509_CRL_XXX functions handle X.509 CRLs.

\fBX509_REQ_XXX, d2i_X509_REQ_XXX, and i2d_X509_REQ_XXX functions handle PKCS#10 certificate requests.

\fBX509_NAME_XXX functions handle certificate names.

\fBX509_ATTRIBUTE_XXX functions handle certificate attributes.

\fBX509_EXTENSION_XXX functions handle certificate extensions.

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), \fBPEM_X509_INFO_read\|(3), \fBd2i_X509\|(3), \fBd2i_X509_ALGOR\|(3), \fBd2i_X509_CRL\|(3), \fBd2i_X509_NAME\|(3), \fBd2i_X509_REQ\|(3), \fBd2i_X509_SIG\|(3), \fBcrypto\|(7) Header "COPYRIGHT" Copyright 2003-2021 The OpenSSL Project Authors. All Rights Reserved.

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>.