X509_NAME_print_ex.pod 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. =pod
  2. =head1 NAME
  3. X509_NAME_print_ex, X509_NAME_print_ex_fp, X509_NAME_print,
  4. X509_NAME_oneline - X509_NAME printing routines.
  5. =head1 SYNOPSIS
  6. #include <openssl/x509.h>
  7. int X509_NAME_print_ex(BIO *out, X509_NAME *nm, int indent, unsigned long flags);
  8. int X509_NAME_print_ex_fp(FILE *fp, X509_NAME *nm, int indent, unsigned long flags);
  9. char * X509_NAME_oneline(X509_NAME *a,char *buf,int size);
  10. int X509_NAME_print(BIO *bp, X509_NAME *name, int obase);
  11. =head1 DESCRIPTION
  12. X509_NAME_print_ex() prints a human readable version of B<nm> to BIO B<out>. Each
  13. line (for multiline formats) is indented by B<indent> spaces. The output format
  14. can be extensively customised by use of the B<flags> parameter.
  15. X509_NAME_print_ex_fp() is identical to X509_NAME_print_ex() except the output is
  16. written to FILE pointer B<fp>.
  17. X509_NAME_oneline() prints an ASCII version of B<a> to B<buf>.
  18. If B<buf> is B<NULL> then a buffer is dynamically allocated and returned, and
  19. B<size> is ignored.
  20. Otherwise, at most B<size> bytes will be written, including the ending '\0',
  21. and B<buf> is returned.
  22. X509_NAME_print() prints out B<name> to B<bp> indenting each line by B<obase>
  23. characters. Multiple lines are used if the output (including indent) exceeds
  24. 80 characters.
  25. =head1 NOTES
  26. The functions X509_NAME_oneline() and X509_NAME_print() are legacy functions which
  27. produce a non standard output form, they don't handle multi character fields and
  28. have various quirks and inconsistencies. Their use is strongly discouraged in new
  29. applications.
  30. Although there are a large number of possible flags for most purposes
  31. B<XN_FLAG_ONELINE>, B<XN_FLAG_MULTILINE> or B<XN_FLAG_RFC2253> will suffice.
  32. As noted on the L<ASN1_STRING_print_ex(3)|ASN1_STRING_print_ex(3)> manual page
  33. for UTF8 terminals the B<ASN1_STRFLGS_ESC_MSB> should be unset: so for example
  34. B<XN_FLAG_ONELINE & ~ASN1_STRFLGS_ESC_MSB> would be used.
  35. The complete set of the flags supported by X509_NAME_print_ex() is listed below.
  36. Several options can be ored together.
  37. The options B<XN_FLAG_SEP_COMMA_PLUS>, B<XN_FLAG_SEP_CPLUS_SPC>,
  38. B<XN_FLAG_SEP_SPLUS_SPC> and B<XN_FLAG_SEP_MULTILINE> determine the field separators
  39. to use. Two distinct separators are used between distinct RelativeDistinguishedName
  40. components and separate values in the same RDN for a multi-valued RDN. Multi-valued
  41. RDNs are currently very rare so the second separator will hardly ever be used.
  42. B<XN_FLAG_SEP_COMMA_PLUS> uses comma and plus as separators. B<XN_FLAG_SEP_CPLUS_SPC>
  43. uses comma and plus with spaces: this is more readable that plain comma and plus.
  44. B<XN_FLAG_SEP_SPLUS_SPC> uses spaced semicolon and plus. B<XN_FLAG_SEP_MULTILINE> uses
  45. spaced newline and plus respectively.
  46. If B<XN_FLAG_DN_REV> is set the whole DN is printed in reversed order.
  47. The fields B<XN_FLAG_FN_SN>, B<XN_FLAG_FN_LN>, B<XN_FLAG_FN_OID>,
  48. B<XN_FLAG_FN_NONE> determine how a field name is displayed. It will
  49. use the short name (e.g. CN) the long name (e.g. commonName) always
  50. use OID numerical form (normally OIDs are only used if the field name is not
  51. recognised) and no field name respectively.
  52. If B<XN_FLAG_SPC_EQ> is set then spaces will be placed around the '=' character
  53. separating field names and values.
  54. If B<XN_FLAG_DUMP_UNKNOWN_FIELDS> is set then the encoding of unknown fields is
  55. printed instead of the values.
  56. If B<XN_FLAG_FN_ALIGN> is set then field names are padded to 20 characters: this
  57. is only of use for multiline format.
  58. Additionally all the options supported by ASN1_STRING_print_ex() can be used to
  59. control how each field value is displayed.
  60. In addition a number options can be set for commonly used formats.
  61. B<XN_FLAG_RFC2253> sets options which produce an output compatible with RFC2253 it
  62. is equivalent to:
  63. B<ASN1_STRFLGS_RFC2253 | XN_FLAG_SEP_COMMA_PLUS | XN_FLAG_DN_REV | XN_FLAG_FN_SN | XN_FLAG_DUMP_UNKNOWN_FIELDS>
  64. B<XN_FLAG_ONELINE> is a more readable one line format which is the same as:
  65. B<ASN1_STRFLGS_RFC2253 | ASN1_STRFLGS_ESC_QUOTE | XN_FLAG_SEP_CPLUS_SPC | XN_FLAG_SPC_EQ | XN_FLAG_FN_SN>
  66. B<XN_FLAG_MULTILINE> is a multiline format which is the same as:
  67. 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>
  68. B<XN_FLAG_COMPAT> uses a format identical to X509_NAME_print(): in fact it calls X509_NAME_print() internally.
  69. =head1 SEE ALSO
  70. L<ASN1_STRING_print_ex(3)|ASN1_STRING_print_ex(3)>
  71. =head1 HISTORY
  72. TBA
  73. =cut