OPENSSL-NAMEDISPLAY-OPTIONS(1SSL)
π OPENSSL-NAMEDISPLAY-OPTIONS π
okay bestie so this is the manual page for openssl-namedisplay-options in the OpenSSL docs, and it's genuinely one of those little pages that ate and left no crumbs. it's all about Distinguished name display options β yeah, the thing that controls how your DNs look when OpenSSL prints them. come sit with me π«Ά
β¨ NAME β¨
openssl-namedisplay-options β Distinguished name display options π
like. it's the vibe controller for how subject and issuer DNs show up on your screen. that's the whole job.
β¨ SYNOPSIS β¨
openssl command [ options ... ] [ parameters ... ]
yep that's literally it, no cap π the real goodies live down in -nameopt.
β¨ DESCRIPTION β¨
okay so here's the tea β OpenSSL gives you fine-grain control over how the subject and issuer DN's are displayed. you do this with the -nameopt option, which takes a comma-separated list of options from the set below. (the set is coming, be patient, it's iconic.)
any option can be preceded by a minus sign, "-", to turn it off. switch it off, bestie, it's your world. and here's the helpful bit: the first four option arguments are the most commonly used β so those are the ones you'll actually be reaching for most days π
the default value is:
"esc_ctrl,utf8,dump_unknown,dump_der,sep_comma_plus_space,sname"
memorise her or don't, but know she's the baseline vibe.
β¨ OPTIONS β¨
πΈ Name Format Option Arguments πΈ
the DN output format can be fine tuned with the following flags. let's go one by one, no skipping, we're thorough in this house π
compatβ display the name using an old format from previous OpenSSL versions. it's giving nostalgia, it's giving legacy π§RFC2253β display the name using the format defined in RFC 2253. it is equivalent toesc_2253,esc_ctrl,esc_msb,utf8,dump_nostr,dump_unknown,dump_der,sep_comma_plus,dn_revandsname. yeah that's a lot of little options doing a group project and honestly? they ate πonelineβ display the name in one line, using a format that is more readable RFC 2253. it is equivalent to theesc_2253,esc_ctrl,esc_msb,utf8,dump_nostr,dump_der,use_quote,sep_comma_plus_space,space_eqandsnameoptions. one line, still classy, still understood πmultilineβ display the name using multiple lines. it is equivalent toesc_ctrl,esc_msb,sep_multiline,space_eq,lnameandalign. she's tall, she's structured, she's a whole staircase of info πesc_2253β escape the "special" characters in a field, as required by RFC 2253. that's any of the characters",+"<>;","#"at the beginning of a string, and leading or trailing spaces. leaving them unescaped is not the move π«esc_2254β escape the "special" characters in a field as required by RFC 2254 in a field. that's the NUL character and the characters"()*".esc_ctrlβ escape non-printable ASCII characters, codes less than0x20(space) or greater than0x7F(DELETE). they get displayed using RFC 2253"\XX"notation whereXXare the two hex digits representing the character value. cute little secret code, honestly π₯esc_msbβ escape any characters with the most significant bit set, that is with values larger than127, as described inesc_ctrl. same energy, higher bits π«use_quoteβ escapes some characters by surrounding the entire string with quotation marks,""". without this option, individual special characters are preceded with a backslash character,"\". pick your fighter, both are valid π€utf8β convert all strings to UTF-8 format first as required by RFC 2253. if the output device is UTF-8 compatible, then using this option (and not settingesc_msb) may give the correct display of multibyte characters β¨ and listen, if this option is not set, then multibyte characters larger than0xFFwill be output as"\UXXXX"for 16 bits or"\WXXXXXXXX"for 32 bits. also, any UTF8Strings will be converted to their character form first. she does the conversion work and the formatting, main character behaviour fr πignore_typeβ this option does not attempt to interpret multibyte characters in any way. that is, the content octets are merely dumped as though one octet represents each character. this is useful for diagnostic purposes but will result in rather odd looking output π like it works, it's just not gonna be pretty. diagnostic girlies, this one's for you.show_typeβ display the type of the ASN1 character string before the value, such as"BMPSTRING: Hello World". so you actually know what you're looking at πdump_derβ any fields that would be output in hex format are displayed using the DER encoding of the field. if not set, just the content octets are displayed. either way, the#XXXX...format of RFC 2253 is used. consistent format, different contents, love that πdump_nostrβ dump non-character strings, such as ASN.1 OCTET STRING. if this option is not set, then non character string types will be displayed as though each content octet represents a single character. ngl this one's a lifesaver when things get weird π₯dump_allβ dump all fields. when this is used withdump_der, this allows the DER encoding of the structure to be unambiguously determined. "unambiguously" is doing so much heavy lifting here and honestly she deserves it πdump_unknownβ dump any field whose OID is not recognised by OpenSSL. mystery OID? we still show her. no gatekeeping π«Άsep_comma_plus,sep_comma_plus_space,sep_semi_plus_space,sep_multilineβ specify the field separators. the first word is used between the Relative Distinguished Names (RDNs) and the second is between multiple Attribute Value Assertions (AVAs). multiple AVAs are very rare and their use is discouraged π« (like, we don't do that here). the options ending in"space"additionally place a space after the separator to make it more readable. thesep_multilinestarts each field on its own line, and uses"plus space"for the AVA separator. it also indents the fields by four characters. the default value issep_comma_plus_space. okay that was a lot but you got it πdn_revβ reverse the fields of the DN as required by RFC 2253. this also reverses the order of multiple AVAs in a field, but this is permissible as there is no ordering on values. flip it, it's fine, nobody's mad πnofname,sname,lname,oidβ specify how the field name is displayed.nofnamedoes not display the field at all (she's mysterious, she's anonymous π).snameuses the "short name" form (CNforcommonNamefor example).lnameuses the long form.oidrepresents the OID in numerical form and is useful for diagnostic purpose.alignβ align field values for a more readable output. only usable withsep_multiline. you can't just use it wherever, she has ONE job and she needs the right conditions πspace_eqβ places spaces round the equal sign,"=", character which follows the field name. breathing room for the equals sign, as she deserves β¨
β¨ COPYRIGHT β¨
Copyright 2000-2025 The OpenSSL Project Authors. All Rights Reserved.
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 in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>. (yes bestie, actually read the license, it's the law and it's also just polite π)
aaaand that's the whole page, we did it π this was OpenSSL 4.0.3, dated 2026-09-29, from the OpenSSL manual pages β that's the version and the date, so you always know what era of the docs you're reading π slay, go beautify some DNs, mwah π ππ¦
π¦ where this page comes from
- ubuntu stonking: openssl 4.0.3-1ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms