diff options
Diffstat (limited to 'secure/lib/libcrypto/man/man3/X509_NAME_print_ex.3')
| -rw-r--r-- | secure/lib/libcrypto/man/man3/X509_NAME_print_ex.3 | 26 |
1 files changed, 14 insertions, 12 deletions
diff --git a/secure/lib/libcrypto/man/man3/X509_NAME_print_ex.3 b/secure/lib/libcrypto/man/man3/X509_NAME_print_ex.3 index 3dd987e2cbab..01069d85c54f 100644 --- a/secure/lib/libcrypto/man/man3/X509_NAME_print_ex.3 +++ b/secure/lib/libcrypto/man/man3/X509_NAME_print_ex.3 @@ -1,5 +1,5 @@ .\" -*- mode: troff; coding: utf-8 -*- -.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45) +.\" Automatically generated by Pod::Man v6.0.2 (Pod::Simple 3.45) .\" .\" Standard preamble: .\" ======================================================================== @@ -52,10 +52,13 @@ . \} .\} .rr rF +.\" +.\" Required to disable full justification in groff 1.23.0. +.if n .ds AD l .\" ======================================================================== .\" .IX Title "X509_NAME_PRINT_EX 3ossl" -.TH X509_NAME_PRINT_EX 3ossl 2025-09-30 3.5.4 OpenSSL +.TH X509_NAME_PRINT_EX 3ossl 2026-04-07 3.5.6 OpenSSL .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l @@ -85,19 +88,18 @@ output format can be extensively customised by use of the \fIflags\fR parameter. except the output is written to FILE pointer \fIfp\fR. .PP \&\fBX509_NAME_oneline()\fR prints an ASCII version of \fIa\fR to \fIbuf\fR. -This supports multi-valued RDNs and escapes \fB/\fR and \fB+\fR characters in values. +This supports multi\-valued RDNs and escapes \fB/\fR and \fB+\fR characters in values. If \fIbuf\fR is \fBNULL\fR then a buffer is dynamically allocated and returned, and \&\fIsize\fR is ignored. -Otherwise, at most \fIsize\fR bytes will be written, including the ending '\e0', +Otherwise, at most \fIsize\fR bytes will be written, including the ending \*(Aq\e0\*(Aq, and \fIbuf\fR is returned. .PP -\&\fBX509_NAME_print()\fR prints out \fIname\fR to \fIbp\fR indenting each line by \fIobase\fR -characters. Multiple lines are used if the output (including indent) exceeds -80 characters. +\&\fBX509_NAME_print()\fR prints out \fIname\fR to \fIbp\fR on a single line. +The \fIobase\fR parameter is ignored and retained only for API compatibility. .SH NOTES .IX Header "NOTES" The functions \fBX509_NAME_oneline()\fR and \fBX509_NAME_print()\fR -produce a non standard output form, they don't handle multi-character fields and +produce a non standard output form, they don\*(Aqt handle multi\-character fields and have various quirks and inconsistencies. Their use is strongly discouraged in new applications and they could be deprecated in a future release. @@ -116,8 +118,8 @@ The options \fBXN_FLAG_SEP_COMMA_PLUS\fR, \fBXN_FLAG_SEP_CPLUS_SPC\fR, \&\fBXN_FLAG_SEP_SPLUS_SPC\fR and \fBXN_FLAG_SEP_MULTILINE\fR 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 +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. .PP \&\fBXN_FLAG_SEP_COMMA_PLUS\fR uses comma and plus as separators. @@ -134,7 +136,7 @@ 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. .PP -If \fBXN_FLAG_SPC_EQ\fR is set then spaces will be placed around the '=' character +If \fBXN_FLAG_SPC_EQ\fR is set then spaces will be placed around the \*(Aq=\*(Aq character separating field names and values. .PP If \fBXN_FLAG_DUMP_UNKNOWN_FIELDS\fR is set then the encoding of unknown fields is @@ -177,7 +179,7 @@ Otherwise, it returns \-1 on error or other values on success. \&\fBASN1_STRING_print_ex\fR\|(3) .SH COPYRIGHT .IX Header "COPYRIGHT" -Copyright 2002\-2020 The OpenSSL Project Authors. All Rights Reserved. +Copyright 2002\-2026 The OpenSSL Project Authors. All Rights Reserved. .PP Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy |