OPENSSL-NAMEDISPLAY-OPTIONS(1ossl)
π openssl-namedisplay-options β bestie edition π
okay so real talk: this is the openssl-namedisplay-options page from the OpenSSL manual, section 1ossl, and it's literally all about making Distinguished Names (DNs) look the way you want them to look. glow-up for your DNs, no cap β¨
πΈ NAME πΈ
openssl-namedisplay-options β Distinguished name display options π«Ά
π¦ SYNOPSIS π¦
openssl command [ options ... ] [ parameters ... ]
β¨ DESCRIPTION β¨
OpenSSL gives you fine-grain control over how the subject and issuer DN's get displayed, and honestly? iconic behavior. π
You control this with the -nameopt option, which takes a comma-separated list of options from the set below. And here's the cute part: any option can be preceded by a minus sign, -, to turn it off. Turn it off!! Loved that for us. π
The first four option arguments are the ones people actually use the most (the main characters, if you will π).
The default value is:
esc_ctrl,utf8,dump_unknown,dump_der,sep_comma_plus_space,sname
π OPTIONS π
π Name Format Option Arguments
The DN output format can be fine-tuned with the following flags. Let's go through every single one, because we don't skip. π
compatβ display the name using an old format from previous OpenSSL versions. retro vibes, vintage aesthetic, but like... old. π°οΈRFC2253β display the name using the format defined in RFC 2253. It's equivalent toesc_2253,esc_ctrl,esc_msb,utf8,dump_nostr,dump_unknown,dump_der,sep_comma_plus,dn_revandsname. a whole bundle, a whole package deal πonelineβ display the name in one line, using a format that is more readable than RFC 2253. It's equivalent toesc_2253,esc_ctrl,esc_msb,utf8,dump_nostr,dump_der,use_quote,sep_comma_plus_space,space_eqandsname. one line, maximum readability, slay β¨multilineβ display the name using multiple lines. It's equivalent toesc_ctrl,esc_msb,sep_multiline,space_eq,lnameandalign. giving very much "spread out and breathe" energy π¬οΈesc_2253β escape the "special" characters in a field, as required by RFC 2253. That is: any of the characters,+"<>;,#at the beginning of a string, and leading or trailing spaces. protect those special lil guys π‘οΈesc_2254β escape the "special" characters in a field as required by RFC 2254 in a field. That is: theNULcharacter and any of()*. different RFC, different special characters, same protective energy πesc_ctrlβ escape non-printable ASCII characters, codes less than0x20(space) or greater than0x7F(DELETE). They get displayed using the RFC 2253"\XX"notation, whereXXare the two hex digits representing the character value. hex digits ate π₯esc_msbβ escape any characters with the most significant bit set, that is, with values larger than127, as described inesc_ctrl. those high-value characters get the escape treatment too πuse_quoteβ escapes some characters by surrounding the entire string with quotation marks,""". Without this option, individual special characters get preceded with a backslash character,"\". pick your fighter: quotes or backslashes π₯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. If this option is not set, then multibyte characters larger than0xFFwill be output as"\UXXXX"for 16 bits or"\WXXXXXXXX"for 32 bits. In addition, anyUTF8Stringswill be converted to their character form first. utf8 hive rise up π§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. ngl it's giving "I woke up and chose chaos" πshow_typeβ display the type of the ASN1 character string before the value, such as"BMPSTRING: Hello World". name AND value, a two-for-one π«Ά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. hex but make it DER π₯dump_nostrβ dump non-character strings, such as ASN.1OCTET STRING. If this option is not set, then non-character string types will be displayed as though each content octet represents a single character. dumping, but make it specifically the non-characters πdump_allβ dump all fields. When this is used withdump_der, this allows the DER encoding of the structure to be unambiguously determined. unambiguously determined!! that's the whole point, bestie π―dump_unknownβ dump any field whose OID is not recognised by OpenSSL. unknown OIDs? we still dump them, we don't ignore them, we're not rude π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. 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. separators, but make them aesthetic β¨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. reverse, reverse! πnofname,sname,lname,oidβ specify how the field name is displayed.nofnamedoes not display the field at all.snameuses the "short name" form (e.g.CNforcommonName).lnameuses the long form.oidrepresents the OID in numerical form and is useful for diagnostic purposes. four whole personality types for displaying a name, pick your vibe πalignβ align field values for a more readable output. Only usable withsep_multiline. β οΈ align slaps but she needssep_multiline, that's her emotional support option πspace_eqβ places spaces round the equal sign,"=", character which follows the field name. breathing room around the=π«§
π 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>. like, legally, read the license, bestie π«Ά
okay and that's the whole page!! this was OpenSSL 3.5.0, dated 2026-09-25 β mwah, thanks for reading, love u, bye!! πβ¨ππ¦
π¦ where this page comes from
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms