.\" $OpenBSD: d2i_X509.3,v 1.5 2016/12/28 03:35:32 schwarze Exp $ .\" OpenSSL 94480b57 Sep 12 23:34:41 2009 +0000 .\" .\" This file was written by Dr. Stephen Henson . .\" Copyright (c) 2002, 2003, 2005, 2009, 2016 The OpenSSL Project. .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in .\" the documentation and/or other materials provided with the .\" distribution. .\" .\" 3. All advertising materials mentioning features or use of this .\" software must display the following acknowledgment: .\" "This product includes software developed by the OpenSSL Project .\" for use in the OpenSSL Toolkit. (http://www.openssl.org/)" .\" .\" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to .\" endorse or promote products derived from this software without .\" prior written permission. For written permission, please contact .\" openssl-core@openssl.org. .\" .\" 5. Products derived from this software may not be called "OpenSSL" .\" nor may "OpenSSL" appear in their names without prior written .\" permission of the OpenSSL Project. .\" .\" 6. Redistributions of any form whatsoever must retain the following .\" acknowledgment: .\" "This product includes software developed by the OpenSSL Project .\" for use in the OpenSSL Toolkit (http://www.openssl.org/)" .\" .\" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY .\" EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR .\" ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, .\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; .\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, .\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED .\" OF THE POSSIBILITY OF SUCH DAMAGE. .\" .Dd $Mdocdate: December 28 2016 $ .Dt D2I_X509 3 .Os .Sh NAME .Nm d2i_X509 , .Nm i2d_X509 , .Nm d2i_X509_bio , .Nm d2i_X509_fp , .Nm i2d_X509_bio , .Nm i2d_X509_fp , .Nm d2i_X509_AUX , .Nm i2d_X509_AUX .Nd decode and encode X.509 certificates .Sh SYNOPSIS .In openssl/x509.h .Ft X509 * .Fo d2i_X509 .Fa "X509 **val_out" .Fa "const unsigned char **der_in" .Fa "long length" .Fc .Ft int .Fo i2d_X509 .Fa "X509 *val_in" .Fa "unsigned char **der_out" .Fc .Ft X509 * .Fo d2i_X509_bio .Fa "BIO *in_bio" .Fa "X509 **val_out" .Fc .Ft X509 * .Fo d2i_X509_fp .Fa "FILE *in_fp" .Fa "X509 **val_out" .Fc .Ft int .Fo i2d_X509_bio .Fa "BIO *out_bio" .Fa "X509 *val_in" .Fc .Ft int .Fo i2d_X509_fp .Fa "FILE *out_fp" .Fa "X509 *val_in" .Fc .Ft X509 * .Fo d2i_X509_AUX .Fa "X509 **val_out" .Fa "const unsigned char **der_in" .Fa "long length" .Fc .Ft int .Fo i2d_X509_AUX .Fa "X509 *val_in" .Fa "unsigned char **der_out" .Fc .Sh DESCRIPTION These functions decode and encode X.509 certificates and some of their substructures. For details about the semantics, examples, caveats, and bugs, see .Xr ASN1_item_d2i 3 . .Pp .Fn d2i_X509 and .Fn i2d_X509 decode and encode an ASN.1 .Vt Certificate structure defined in RFC 5280 section 4.1. .Pp .Fn d2i_X509_bio , .Fn d2i_X509_fp , .Fn i2d_X509_bio , and .Fn i2d_X509_fp are similar except that they decode or encode using a .Vt BIO or .Vt FILE pointer. .Pp .Fn d2i_X509_AUX is similar to .Fn d2i_X509 , but the input is expected to consist of an X.509 certificate followed by auxiliary trust information. This is used by the PEM routines to read TRUSTED CERTIFICATE objects. This function should not be called on untrusted input. .Pp .Fn i2d_X509_AUX is similar to .Fn i2d_X509 , but the encoded output contains both the certificate and any auxiliary trust information. This is used by the PEM routines to write TRUSTED CERTIFICATE objects. Note that this is a non-standard OpenSSL-specific data format. .Sh RETURN VALUES .Fn d2i_X509 , .Fn d2i_X509_bio , .Fn d2i_X509_fp , and .Fn d2i_X509_AUX return a valid .Vt X509 structure or .Dv NULL if an error occurs. .Pp .Fn i2d_X509 and .Fn i2d_X509_AUX return the number of bytes successfully encoded or a negative value if an error occurs. .Pp .Fn i2d_X509_bio and .Fn i2d_X509_fp return 1 for success or 0 if an error occurs. .Pp For all functions, the error code can be obtained by .Xr ERR_get_error 3 . .Sh SEE ALSO .Xr ASN1_item_d2i 3 , .Xr X509_new 3 .Sh STANDARDS RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile .Sh HISTORY .Fn d2i_X509 , .Fn i2d_X509 , .Fn d2i_X509_bio , .Fn d2i_X509_fp , .Fn i2d_X509_bio , and .Fn i2d_X509_fp are available in all versions of SSLeay and OpenSSL.