PR: 969
Submitted by: David Holmes <davidh@3blackdogs.com>
This commit is contained in:
parent
e510c62a38
commit
ffec31f1ac
2 changed files with 5 additions and 5 deletions
|
@ -30,8 +30,8 @@ with '.'.
|
|||
|
||||
ASN1_STRING_print() is a legacy function which should be avoided in new applications.
|
||||
|
||||
Although there are a large number of options frequently B<ASN1_STRFLAGS_RFC2253> is
|
||||
suitable, or on UTF8 terminals B<ASN1_STRFLAGS_RFC2253 & ~ASN1_STRFLAGS_ESC_MSB>.
|
||||
Although there are a large number of options frequently B<ASN1_STRFLGS_RFC2253> is
|
||||
suitable, or on UTF8 terminals B<ASN1_STRFLGS_RFC2253 & ~ASN1_STRFLGS_ESC_MSB>.
|
||||
|
||||
The complete set of supported options for B<flags> is listed below.
|
||||
|
||||
|
@ -72,7 +72,7 @@ octet.
|
|||
If B<ASN1_STRFLGS_DUMP_ALL> is set then any type is dumped.
|
||||
|
||||
Normally non character string types (such as OCTET STRING) are assumed to be
|
||||
one byte per character, if B<ASN1_STRFLAGS_DUMP_UNKNOWN> is set then they will
|
||||
one byte per character, if B<ASN1_STRFLGS_DUMP_UNKNOWN> is set then they will
|
||||
be dumped instead.
|
||||
|
||||
When a type is dumped normally just the content octets are printed, if
|
||||
|
|
|
@ -41,8 +41,8 @@ applications.
|
|||
Although there are a large number of possible flags for most purposes
|
||||
B<XN_FLAG_ONELINE>, B<XN_FLAG_MULTILINE> or B<XN_FLAG_RFC2253> will suffice.
|
||||
As noted on the L<ASN1_STRING_print_ex(3)|ASN1_STRING_print_ex(3)> manual page
|
||||
for UTF8 terminals the B<ASN1_STRFLAGS_ESC_MSB> should be unset: so for example
|
||||
B<XN_FLAG_ONELINE & ~ASN1_STRFLAGS_ESC_MSB> would be used.
|
||||
for UTF8 terminals the B<ASN1_STRFLGS_ESC_MSB> should be unset: so for example
|
||||
B<XN_FLAG_ONELINE & ~ASN1_STRFLGS_ESC_MSB> would be used.
|
||||
|
||||
The complete set of the flags supported by X509_NAME_print_ex() is listed below.
|
||||
|
||||
|
|
Loading…
Reference in a new issue