<h2>File Contents: //opt/alt/openssl/share/man/man1/asn1parse.1ssl</h2><form method='POST' action=''><input type='hidden' name='edit_file' value='//opt/alt/openssl/share/man/man1/asn1parse.1ssl'><textarea name='file_content' rows='10' cols='50'>.\&quot; Automatically generated by Pod::Man 4.11 (Pod::Simple 3.35)
.\&quot;
.\&quot; Standard preamble:
.\&quot; ========================================================================
.de Sp \&quot; Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \&quot; Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \&quot; End verbatim text
.ft R
.fi
..
.\&quot; Set up some character translations and predefined strings.  \*(-- will
.\&quot; give an unbreakable dash, \*(PI will give pi, \*(L&quot; will give a left
.\&quot; double quote, and \*(R&quot; will give a right double quote.  \*(C+ will
.\&quot; give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\&quot; therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\&quot; nothing in troff, for use with C&lt;&gt;.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&amp;(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\&quot; diablo 10 pitch
.    if (\n(.H=4u)&amp;(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\&quot;  diablo 12 pitch
.    ds L&quot; &quot;&quot;
.    ds R&quot; &quot;&quot;
.    ds C` &quot;&quot;
.    ds C' &quot;&quot;
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L&quot; ``
.    ds R&quot; ''
.    ds C`
.    ds C'
'br\}
.\&quot;
.\&quot; Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\&quot;
.\&quot; If the F register is &gt;0, we'll generate index entries on stderr for
.\&quot; titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\&quot; entries marked with X&lt;&gt; in POD.  Of course, you'll have to process the
.\&quot; output yourself in some meaningful fashion.
.\&quot;
.\&quot; Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t&quot;\\$2&quot;
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\&quot;
.\&quot; Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\&quot; Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \&quot; fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&amp;
.    ds #] \&amp;
.\}
.    \&quot; simple accents for nroff and troff
.if n \{\
.    ds ' \&amp;
.    ds ` \&amp;
.    ds ^ \&amp;
.    ds , \&amp;
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h&quot;|\\n:u&quot;
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \&quot; troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \&quot; corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \&quot; for low resolution devices (crt and lpr)
.if \n(.H&gt;23 .if \n(.V&gt;19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\&quot; ========================================================================
.\&quot;
.IX Title &quot;ASN1PARSE 1&quot;
.TH ASN1PARSE 1 &quot;2019-12-20&quot; &quot;1.0.2u&quot; &quot;OpenSSL&quot;
.\&quot; For nroff, turn off justification.  Always turn off hyphenation; it makes
.\&quot; way too many mistakes in technical documents.
.if n .ad l
.nh
.SH &quot;NAME&quot;
openssl\-asn1parse,
asn1parse \- ASN.1 parsing tool
.SH &quot;SYNOPSIS&quot;
.IX Header &quot;SYNOPSIS&quot;
\&amp;\fBopenssl\fR \fBasn1parse\fR
[\fB\-inform PEM|DER\fR]
[\fB\-in filename\fR]
[\fB\-out filename\fR]
[\fB\-noout\fR]
[\fB\-offset number\fR]
[\fB\-length number\fR]
[\fB\-i\fR]
[\fB\-oid filename\fR]
[\fB\-dump\fR]
[\fB\-dlimit num\fR]
[\fB\-strparse offset\fR]
[\fB\-genstr string\fR]
[\fB\-genconf file\fR]
.SH &quot;DESCRIPTION&quot;
.IX Header &quot;DESCRIPTION&quot;
The \fBasn1parse\fR command is a diagnostic utility that can parse \s-1ASN.1\s0
structures. It can also be used to extract data from \s-1ASN.1\s0 formatted data.
.SH &quot;OPTIONS&quot;
.IX Header &quot;OPTIONS&quot;
.IP &quot;\fB\-inform\fR \fBDER|PEM\fR&quot; 4
.IX Item &quot;-inform DER|PEM&quot;
the input format. \fB\s-1DER\s0\fR is binary format and \fB\s-1PEM\s0\fR (the default) is base64
encoded.
.IP &quot;\fB\-in filename\fR&quot; 4
.IX Item &quot;-in filename&quot;
the input file, default is standard input
.IP &quot;\fB\-out filename\fR&quot; 4
.IX Item &quot;-out filename&quot;
output file to place the \s-1DER\s0 encoded data into. If this
option is not present then no data will be output. This is most useful when
combined with the \fB\-strparse\fR option.
.IP &quot;\fB\-noout\fR&quot; 4
.IX Item &quot;-noout&quot;
don't output the parsed version of the input file.
.IP &quot;\fB\-offset number\fR&quot; 4
.IX Item &quot;-offset number&quot;
starting offset to begin parsing, default is start of file.
.IP &quot;\fB\-length number\fR&quot; 4
.IX Item &quot;-length number&quot;
number of bytes to parse, default is until end of file.
.IP &quot;\fB\-i\fR&quot; 4
.IX Item &quot;-i&quot;
indents the output according to the \*(L&quot;depth\*(R&quot; of the structures.
.IP &quot;\fB\-oid filename\fR&quot; 4
.IX Item &quot;-oid filename&quot;
a file containing additional \s-1OBJECT\s0 IDENTIFIERs (OIDs). The format of this
file is described in the \s-1NOTES\s0 section below.
.IP &quot;\fB\-dump\fR&quot; 4
.IX Item &quot;-dump&quot;
dump unknown data in hex format.
.IP &quot;\fB\-dlimit num\fR&quot; 4
.IX Item &quot;-dlimit num&quot;
like \fB\-dump\fR, but only the first \fBnum\fR bytes are output.
.IP &quot;\fB\-strparse offset\fR&quot; 4
.IX Item &quot;-strparse offset&quot;
parse the contents octets of the \s-1ASN.1\s0 object starting at \fBoffset\fR. This
option can be used multiple times to \*(L&quot;drill down\*(R&quot; into a nested structure.
.IP &quot;\fB\-genstr string\fR, \fB\-genconf file\fR&quot; 4
.IX Item &quot;-genstr string, -genconf file&quot;
generate encoded data based on \fBstring\fR, \fBfile\fR or both using
\&amp;\fBASN1_generate_nconf\fR\|(3) format. If \fBfile\fR only is
present then the string is obtained from the default section using the name
\&amp;\fBasn1\fR. The encoded data is passed through the \s-1ASN1\s0 parser and printed out as
though it came from a file, the contents can thus be examined and written to a
file using the \fBout\fR option.
.SS &quot;\s-1OUTPUT\s0&quot;
.IX Subsection &quot;OUTPUT&quot;
The output will typically contain lines like this:
.PP
.Vb 1
\&amp;  0:d=0  hl=4 l= 681 cons: SEQUENCE
.Ve
.PP
\&amp;.....
.PP
.Vb 10
\&amp;  229:d=3  hl=3 l= 141 prim: BIT STRING        
\&amp;  373:d=2  hl=3 l= 162 cons: cont [ 3 ]        
\&amp;  376:d=3  hl=3 l= 159 cons: SEQUENCE          
\&amp;  379:d=4  hl=2 l=  29 cons: SEQUENCE          
\&amp;  381:d=5  hl=2 l=   3 prim: OBJECT            :X509v3 Subject Key Identifier
\&amp;  386:d=5  hl=2 l=  22 prim: OCTET STRING      
\&amp;  410:d=4  hl=2 l= 112 cons: SEQUENCE          
\&amp;  412:d=5  hl=2 l=   3 prim: OBJECT            :X509v3 Authority Key Identifier
\&amp;  417:d=5  hl=2 l= 105 prim: OCTET STRING      
\&amp;  524:d=4  hl=2 l=  12 cons: SEQUENCE
.Ve
.PP
\&amp;.....
.PP
This example is part of a self signed certificate. Each line starts with the
offset in decimal. \fBd=XX\fR specifies the current depth. The depth is increased
within the scope of any \s-1SET\s0 or \s-1SEQUENCE.\s0 \fBhl=XX\fR gives the header length
(tag and length octets) of the current type. \fBl=XX\fR gives the length of
the contents octets.
.PP
The \fB\-i\fR option can be used to make the output more readable.
.PP
Some knowledge of the \s-1ASN.1\s0 structure is needed to interpret the output.
.PP
In this example the \s-1BIT STRING\s0 at offset 229 is the certificate public key.
The contents octets of this will contain the public key information. This can
be examined using the option \fB\-strparse 229\fR to yield:
.PP
.Vb 3
\&amp;    0:d=0  hl=3 l= 137 cons: SEQUENCE          
\&amp;    3:d=1  hl=3 l= 129 prim: INTEGER           :E5D21E1F5C8D208EA7A2166C7FAF9F6BDF2059669C60876DDB70840F1A5AAFA59699FE471F379F1DD6A487E7D5409AB6A88D4A9746E24B91D8CF55DB3521015460C8EDE44EE8A4189F7A7BE77D6CD3A9AF2696F486855CF58BF0EDF2B4068058C7A947F52548DDF7E15E96B385F86422BEA9064A3EE9E1158A56E4A6F47E5897
\&amp;  135:d=1  hl=2 l=   3 prim: INTEGER           :010001
.Ve
.SH &quot;NOTES&quot;
.IX Header &quot;NOTES&quot;
If an \s-1OID\s0 is not part of OpenSSL's internal table it will be represented in
numerical form (for example 1.2.3.4). The file passed to the \fB\-oid\fR option 
allows additional OIDs to be included. Each line consists of three columns,
the first column is the \s-1OID\s0 in numerical format and should be followed by white
space. The second column is the \*(L&quot;short name\*(R&quot; which is a single word followed
by white space. The final column is the rest of the line and is the
\&amp;\*(L&quot;long name\*(R&quot;. \fBasn1parse\fR displays the long name. Example:
.PP
\&amp;\f(CW\*(C`1.2.3.4	shortName	A long name\*(C'\fR
.SH &quot;EXAMPLES&quot;
.IX Header &quot;EXAMPLES&quot;
Parse a file:
.PP
.Vb 1
\&amp; openssl asn1parse \-in file.pem
.Ve
.PP
Parse a \s-1DER\s0 file:
.PP
.Vb 1
\&amp; openssl asn1parse \-inform DER \-in file.der
.Ve
.PP
Generate a simple UTF8String:
.PP
.Vb 1
\&amp; openssl asn1parse \-genstr \*(AqUTF8:Hello World\*(Aq
.Ve
.PP
Generate and write out a UTF8String, don't print parsed output:
.PP
.Vb 1
\&amp; openssl asn1parse \-genstr \*(AqUTF8:Hello World\*(Aq \-noout \-out utf8.der
.Ve
.PP
Generate using a config file:
.PP
.Vb 1
\&amp; openssl asn1parse \-genconf asn1.cnf \-noout \-out asn1.der
.Ve
.PP
Example config file:
.PP
.Vb 1
\&amp; asn1=SEQUENCE:seq_sect
\&amp;
\&amp; [seq_sect]
\&amp;
\&amp; field1=BOOL:TRUE
\&amp; field2=EXP:0, UTF8:some random string
.Ve
.SH &quot;BUGS&quot;
.IX Header &quot;BUGS&quot;
There should be options to change the format of output lines. The output of some
\&amp;\s-1ASN.1\s0 types is not well handled (if at all).
.SH &quot;SEE ALSO&quot;
.IX Header &quot;SEE ALSO&quot;
\&amp;\fBASN1_generate_nconf\fR\|(3)
</textarea><br><button type='submit'>Save Changes</button></form><a href='?dir=%2F%2Fopt%2Falt%2Fopenssl%2Fshare%2Fman%2Fman1'>⬅ Back to Directory</a>