5 X509_NAME_print_ex, X509_NAME_print_ex_fp, X509_NAME_print,
6 X509_NAME_oneline - X509_NAME printing routines
10 #include <openssl/x509.h>
12 int X509_NAME_print_ex(BIO *out, const X509_NAME *nm, int indent, unsigned long flags);
13 int X509_NAME_print_ex_fp(FILE *fp, const X509_NAME *nm, int indent, unsigned long flags);
14 char * X509_NAME_oneline(const X509_NAME *a, char *buf, int size);
15 int X509_NAME_print(BIO *bp, const X509_NAME *name, int obase);
19 X509_NAME_print_ex() prints a human readable version of B<nm> to BIO B<out>. Each
20 line (for multiline formats) is indented by B<indent> spaces. The output format
21 can be extensively customised by use of the B<flags> parameter.
23 X509_NAME_print_ex_fp() is identical to X509_NAME_print_ex() except the output is
24 written to FILE pointer B<fp>.
26 X509_NAME_oneline() prints an ASCII version of B<a> to B<buf>.
27 If B<buf> is B<NULL> then a buffer is dynamically allocated and returned, and
29 Otherwise, at most B<size> bytes will be written, including the ending '\0',
30 and B<buf> is returned.
32 X509_NAME_print() prints out B<name> to B<bp> indenting each line by B<obase>
33 characters. Multiple lines are used if the output (including indent) exceeds
38 The functions X509_NAME_oneline() and X509_NAME_print() are legacy functions which
39 produce a non standard output form, they don't handle multi character fields and
40 have various quirks and inconsistencies. Their use is strongly discouraged in new
43 Although there are a large number of possible flags for most purposes
44 B<XN_FLAG_ONELINE>, B<XN_FLAG_MULTILINE> or B<XN_FLAG_RFC2253> will suffice.
45 As noted on the L<ASN1_STRING_print_ex(3)> manual page
46 for UTF8 terminals the B<ASN1_STRFLGS_ESC_MSB> should be unset: so for example
47 B<XN_FLAG_ONELINE & ~ASN1_STRFLGS_ESC_MSB> would be used.
49 The complete set of the flags supported by X509_NAME_print_ex() is listed below.
51 Several options can be ored together.
53 The options B<XN_FLAG_SEP_COMMA_PLUS>, B<XN_FLAG_SEP_CPLUS_SPC>,
54 B<XN_FLAG_SEP_SPLUS_SPC> and B<XN_FLAG_SEP_MULTILINE> determine the field separators
55 to use. Two distinct separators are used between distinct RelativeDistinguishedName
56 components and separate values in the same RDN for a multi-valued RDN. Multi-valued
57 RDNs are currently very rare so the second separator will hardly ever be used.
59 B<XN_FLAG_SEP_COMMA_PLUS> uses comma and plus as separators. B<XN_FLAG_SEP_CPLUS_SPC>
60 uses comma and plus with spaces: this is more readable that plain comma and plus.
61 B<XN_FLAG_SEP_SPLUS_SPC> uses spaced semicolon and plus. B<XN_FLAG_SEP_MULTILINE> uses
62 spaced newline and plus respectively.
64 If B<XN_FLAG_DN_REV> is set the whole DN is printed in reversed order.
66 The fields B<XN_FLAG_FN_SN>, B<XN_FLAG_FN_LN>, B<XN_FLAG_FN_OID>,
67 B<XN_FLAG_FN_NONE> determine how a field name is displayed. It will
68 use the short name (e.g. CN) the long name (e.g. commonName) always
69 use OID numerical form (normally OIDs are only used if the field name is not
70 recognised) and no field name respectively.
72 If B<XN_FLAG_SPC_EQ> is set then spaces will be placed around the '=' character
73 separating field names and values.
75 If B<XN_FLAG_DUMP_UNKNOWN_FIELDS> is set then the encoding of unknown fields is
76 printed instead of the values.
78 If B<XN_FLAG_FN_ALIGN> is set then field names are padded to 20 characters: this
79 is only of use for multiline format.
81 Additionally all the options supported by ASN1_STRING_print_ex() can be used to
82 control how each field value is displayed.
84 In addition a number options can be set for commonly used formats.
86 B<XN_FLAG_RFC2253> sets options which produce an output compatible with RFC2253 it
88 B<ASN1_STRFLGS_RFC2253 | XN_FLAG_SEP_COMMA_PLUS | XN_FLAG_DN_REV | XN_FLAG_FN_SN | XN_FLAG_DUMP_UNKNOWN_FIELDS>
91 B<XN_FLAG_ONELINE> is a more readable one line format which is the same as:
92 B<ASN1_STRFLGS_RFC2253 | ASN1_STRFLGS_ESC_QUOTE | XN_FLAG_SEP_CPLUS_SPC | XN_FLAG_SPC_EQ | XN_FLAG_FN_SN>
94 B<XN_FLAG_MULTILINE> is a multiline format which is the same as:
95 B<ASN1_STRFLGS_ESC_CTRL | ASN1_STRFLGS_ESC_MSB | XN_FLAG_SEP_MULTILINE | XN_FLAG_SPC_EQ | XN_FLAG_FN_LN | XN_FLAG_FN_ALIGN>
97 B<XN_FLAG_COMPAT> uses a format identical to X509_NAME_print(): in fact it calls X509_NAME_print() internally.
101 L<ASN1_STRING_print_ex(3)>
105 Copyright 2002-2016 The OpenSSL Project Authors. All Rights Reserved.
107 Licensed under the OpenSSL license (the "License"). You may not use
108 this file except in compliance with the License. You can obtain a copy
109 in the file LICENSE in the source distribution or at
110 L<https://www.openssl.org/source/license.html>.