X509NAMEprintex(3) OpenSSL X509NAMEprintex(3)

NAME
       X509NAMEprintex, X509NAMEprintexfp, X509NAMEprint,
       X509NAMEoneline - X509NAME printing routines.

SYNOPSIS
        #include 

        int X509NAMEprintex(BIO *out, X509NAME *nm, int indent, unsigned long flags);
        int X509NAMEprintexfp(FILE *fp, X509NAME *nm, int indent, unsigned long flags);
        char * X509NAMEoneline(X509NAME *a,char *buf,int size);
        int X509NAMEprint(BIO *bp, X509NAME *name, int obase);

DESCRIPTION
       X509NAMEprintex() prints a human readable version of nnmm to BIO oouutt.
       Each line (for multiline formats) is indented by iinnddeenntt spaces. The
       output format can be extensively customised by use of the ffllaaggss
       parameter.

       X509NAMEprintexfp() is identical to X509NAMEprintex() except the
       output is written to FILE pointer ffpp.

       X509NAMEoneline() prints an ASCII version of aa to bbuuff. At most ssiizzee
       bytes will be written. If bbuuff is NNUULLLL then a buffer is dynamically
       allocated and returned, otherwise bbuuff is returned.

       X509NAMEprint() prints out nnaammee to bbpp indenting each line by oobbaassee
       characters. Multiple lines are used if the output (including indent)
       exceeds 80 characters.

NNOOTTEESS
       The functions X509NAMEoneline() and X509NAMEprint() are legacy
       functions which produce a non standard output form, they don't handle
       multi character fields and have various quirks and inconsistencies.
       Their use is strongly discouraged in new applications.

       Although there are a large number of possible flags for most purposes
       XXNNFFLLAAGGOONNEELLIINNEE, XXNNFFLLAAGGMMUULLTTIILLIINNEE or XXNNFFLLAAGGRRFFCC22225533 will suffice.  As
       noted on the ASN1STRINGprintex(3) manual page for UTF8 terminals the
       AASSNN11SSTTRRFFLLGGSSEESSCCMMSSBB should be unset: so for example XXNNFFLLAAGGOONNEELLIINNEE &&
       ~~AASSNN11SSTTRRFFLLGGSSEESSCCMMSSBB would be used.

       The complete set of the flags supported by X509NAMEprintex() is
       listed below.

       Several options can be ored together.

       The options XXNNFFLLAAGGSSEEPPCCOOMMMMAAPPLLUUSS, XXNNFFLLAAGGSSEEPPCCPPLLUUSSSSPPCC,
       XXNNFFLLAAGGSSEEPPSSPPLLUUSSSSPPCC and XXNNFFLLAAGGSSEEPPMMUULLTTIILLIINNEE determine the field
       separators to use. Two distinct separators are used between distinct
       RelativeDistinguishedName components and separate values in the same
       RDN for a multi-valued RDN. Multi-valued RDNs are currently very rare
       so the second separator will hardly ever be used.

       XXNNFFLLAAGGSSEEPPCCOOMMMMAAPPLLUUSS uses comma and plus as separators.
       XXNNFFLLAAGGSSEEPPCCPPLLUUSSSSPPCC uses comma and plus with spaces: this is more
       readable that plain comma and plus.  XXNNFFLLAAGGSSEEPPSSPPLLUUSSSSPPCC uses spaced
       semicolon and plus. XXNNFFLLAAGGSSEEPPMMUULLTTIILLIINNEE uses spaced newline and plus
       respectively.

       If XXNNFFLLAAGGDDNNRREEVV is set the whole DN is printed in reversed order.

       The fields XXNNFFLLAAGGFFNNSSNN, XXNNFFLLAAGGFFNNLLNN, XXNNFFLLAAGGFFNNOOIIDD,
       XXNNFFLLAAGGFFNNNNOONNEE determine how a field name is displayed. It will use
       the short name (e.g. CN) the long name (e.g. commonName) always use OID
       numerical form (normally OIDs are only used if the field name is not
       recognised) and no field name respectively.

       If XXNNFFLLAAGGSSPPCCEEQQ is set then spaces will be placed around the '='
       character separating field names and values.

       If XXNNFFLLAAGGDDUUMMPPUUNNKKNNOOWWNNFFIIEELLDDSS is set then the encoding of unknown
       fields is printed instead of the values.

       If XXNNFFLLAAGGFFNNAALLIIGGNN is set then field names are padded to 20
       characters: this is only of use for multiline format.

       Additionally all the options supported by ASN1STRINGprintex() can be
       used to control how each field value is displayed.

       In addition a number options can be set for commonly used formats.

       XXNNFFLLAAGGRRFFCC22225533 sets options which produce an output compatible with
       RFC2253 it is equivalent to:
        AASSNN11SSTTRRFFLLGGSSRRFFCC22225533 || XXNNFFLLAAGGSSEEPPCCOOMMMMAAPPLLUUSS || XXNNFFLLAAGGDDNNRREEVV ||
       XXNNFFLLAAGGFFNNSSNN || XXNNFFLLAAGGDDUUMMPPUUNNKKNNOOWWNNFFIIEELLDDSS

       XXNNFFLLAAGGOONNEELLIINNEE is a more readable one line format it is the same as:
        AASSNN11SSTTRRFFLLGGSSRRFFCC22225533 || AASSNN11SSTTRRFFLLGGSSEESSCCQQUUOOTTEE || XXNNFFLLAAGGSSEEPPCCPPLLUUSSSSPPCC
       || XXNNFFLLAAGGSSPPCCEEQQ || XXNNFFLLAAGGFFNNSSNN

       XXNNFFLLAAGGMMUULLTTIILLIINNEE is a multiline format is is the same as:
        AASSNN11SSTTRRFFLLGGSSEESSCCCCTTRRLL || AASSNN11SSTTRRFFLLGGSSEESSCCMMSSBB || XXNNFFLLAAGGSSEEPPMMUULLTTIILLIINNEE ||
       XXNNFFLLAAGGSSPPCCEEQQ || XXNNFFLLAAGGFFNNLLNN || XXNNFFLLAAGGFFNNAALLIIGGNN

       XXNNFFLLAAGGCCOOMMPPAATT uses a format identical to X509NAMEprint(): in fact it
       calls X509NAMEprint() internally.

SEE ALSO
       ASN1STRINGprintex(3)

HISTORY       TBA



0.9.7l                            2004-11-13             X509NAMEprintex(3)