1 .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
4 .\" ========================================================================
5 .de Sh \" Subsection heading
13 .de Sp \" Vertical space (when we can't use .PP)
17 .de Vb \" Begin verbatim text
22 .de Ve \" End verbatim text
26 .\" Set up some character translations and predefined strings. \*(-- will
27 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
28 .\" double quote, and \*(R" will give a right double quote. | will give a
29 .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
30 .\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
31 .\" expand to `' in nroff, nothing in troff, for use with C<>.
33 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
37 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
38 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
51 .\" If the F register is turned on, we'll generate index entries on stderr for
52 .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
53 .\" entries marked with X<> in POD. Of course, you'll have to process the
54 .\" output yourself in some meaningful fashion.
57 . tm Index:\\$1\t\\n%\t"\\$2"
63 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
64 .\" way too many mistakes in technical documents.
68 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
69 .\" Fear. Run. Save yourself. No user-serviceable parts.
70 . \" fudge factors for nroff and troff
79 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
85 . \" simple accents for nroff and troff
95 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
96 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
97 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
98 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
99 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
100 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
102 . \" troff and (daisy-wheel) nroff accents
103 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
104 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
105 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
106 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
107 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
108 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
109 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
110 .ds ae a\h'-(\w'a'u*4/10)'e
111 .ds Ae A\h'-(\w'A'u*4/10)'E
112 . \" corrections for vroff
113 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
114 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
115 . \" for low resolution devices (crt and lpr)
116 .if \n(.H>23 .if \n(.V>19 \
129 .\" ========================================================================
131 .IX Title "ASN1PARSE 1"
132 .TH ASN1PARSE 1 "2004-12-18" "0.9.7e" "OpenSSL"
134 asn1parse \- ASN.1 parsing tool
136 .IX Header "SYNOPSIS"
137 \&\fBopenssl\fR \fBasn1parse\fR
138 [\fB\-inform PEM|DER\fR]
139 [\fB\-in filename\fR]
140 [\fB\-out filename\fR]
142 [\fB\-offset number\fR]
143 [\fB\-length number\fR]
145 [\fB\-oid filename\fR]
146 [\fB\-strparse offset\fR]
148 .IX Header "DESCRIPTION"
149 The \fBasn1parse\fR command is a diagnostic utility that can parse \s-1ASN\s0.1
150 structures. It can also be used to extract data from \s-1ASN\s0.1 formatted data.
153 .IP "\fB\-inform\fR \fBDER|PEM\fR" 4
154 .IX Item "-inform DER|PEM"
155 the input format. \fB\s-1DER\s0\fR is binary format and \fB\s-1PEM\s0\fR (the default) is base64
157 .IP "\fB\-in filename\fR" 4
158 .IX Item "-in filename"
159 the input file, default is standard input
160 .IP "\fB\-out filename\fR" 4
161 .IX Item "-out filename"
162 output file to place the \s-1DER\s0 encoded data into. If this
163 option is not present then no data will be output. This is most useful when
164 combined with the \fB\-strparse\fR option.
165 .IP "\fB\-noout\fR" 4
167 don't output the parsed version of the input file.
168 .IP "\fB\-offset number\fR" 4
169 .IX Item "-offset number"
170 starting offset to begin parsing, default is start of file.
171 .IP "\fB\-length number\fR" 4
172 .IX Item "-length number"
173 number of bytes to parse, default is until end of file.
176 indents the output according to the \*(L"depth\*(R" of the structures.
177 .IP "\fB\-oid filename\fR" 4
178 .IX Item "-oid filename"
179 a file containing additional \s-1OBJECT\s0 IDENTIFIERs (OIDs). The format of this
180 file is described in the \s-1NOTES\s0 section below.
181 .IP "\fB\-strparse offset\fR" 4
182 .IX Item "-strparse offset"
183 parse the contents octets of the \s-1ASN\s0.1 object starting at \fBoffset\fR. This
184 option can be used multiple times to \*(L"drill down\*(R" into a nested structure.
186 .IX Subsection "OUTPUT"
187 The output will typically contain lines like this:
190 \& 0:d=0 hl=4 l= 681 cons: SEQUENCE
196 \& 229:d=3 hl=3 l= 141 prim: BIT STRING
197 \& 373:d=2 hl=3 l= 162 cons: cont [ 3 ]
198 \& 376:d=3 hl=3 l= 159 cons: SEQUENCE
199 \& 379:d=4 hl=2 l= 29 cons: SEQUENCE
200 \& 381:d=5 hl=2 l= 3 prim: OBJECT :X509v3 Subject Key Identifier
201 \& 386:d=5 hl=2 l= 22 prim: OCTET STRING
202 \& 410:d=4 hl=2 l= 112 cons: SEQUENCE
203 \& 412:d=5 hl=2 l= 3 prim: OBJECT :X509v3 Authority Key Identifier
204 \& 417:d=5 hl=2 l= 105 prim: OCTET STRING
205 \& 524:d=4 hl=2 l= 12 cons: SEQUENCE
210 This example is part of a self signed certificate. Each line starts with the
211 offset in decimal. \fBd=XX\fR specifies the current depth. The depth is increased
212 within the scope of any \s-1SET\s0 or \s-1SEQUENCE\s0. \fBhl=XX\fR gives the header length
213 (tag and length octets) of the current type. \fBl=XX\fR gives the length of
216 The \fB\-i\fR option can be used to make the output more readable.
218 Some knowledge of the \s-1ASN\s0.1 structure is needed to interpret the output.
220 In this example the \s-1BIT\s0 \s-1STRING\s0 at offset 229 is the certificate public key.
221 The contents octets of this will contain the public key information. This can
222 be examined using the option \fB\-strparse 229\fR to yield:
225 \& 0:d=0 hl=3 l= 137 cons: SEQUENCE
226 \& 3:d=1 hl=3 l= 129 prim: INTEGER :E5D21E1F5C8D208EA7A2166C7FAF9F6BDF2059669C60876DDB70840F1A5AAFA59699FE471F379F1DD6A487E7D5409AB6A88D4A9746E24B91D8CF55DB3521015460C8EDE44EE8A4189F7A7BE77D6CD3A9AF2696F486855CF58BF0EDF2B4068058C7A947F52548DDF7E15E96B385F86422BEA9064A3EE9E1158A56E4A6F47E5897
227 \& 135:d=1 hl=2 l= 3 prim: INTEGER :010001
231 If an \s-1OID\s0 is not part of OpenSSL's internal table it will be represented in
232 numerical form (for example 1.2.3.4). The file passed to the \fB\-oid\fR option
233 allows additional OIDs to be included. Each line consists of three columns,
234 the first column is the \s-1OID\s0 in numerical format and should be followed by white
235 space. The second column is the \*(L"short name\*(R" which is a single word followed
236 by white space. The final column is the rest of the line and is the
237 \&\*(L"long name\*(R". \fBasn1parse\fR displays the long name. Example:
239 \&\f(CW\*(C`1.2.3.4 shortName A long name\*(C'\fR
242 There should be options to change the format of input lines. The output of some
243 \&\s-1ASN\s0.1 types is not well handled (if at all).