asn1parse.pod 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175
  1. =pod
  2. =head1 NAME
  3. asn1parse - ASN.1 parsing tool
  4. =head1 SYNOPSIS
  5. B<openssl> B<asn1parse>
  6. [B<-inform PEM|DER>]
  7. [B<-in filename>]
  8. [B<-out filename>]
  9. [B<-noout>]
  10. [B<-offset number>]
  11. [B<-length number>]
  12. [B<-i>]
  13. [B<-oid filename>]
  14. [B<-strparse offset>]
  15. [B<-genstr string>]
  16. [B<-genconf file>]
  17. =head1 DESCRIPTION
  18. The B<asn1parse> command is a diagnostic utility that can parse ASN.1
  19. structures. It can also be used to extract data from ASN.1 formatted data.
  20. =head1 OPTIONS
  21. =over 4
  22. =item B<-inform> B<DER|PEM>
  23. the input format. B<DER> is binary format and B<PEM> (the default) is base64
  24. encoded.
  25. =item B<-in filename>
  26. the input file, default is standard input
  27. =item B<-out filename>
  28. output file to place the DER encoded data into. If this
  29. option is not present then no data will be output. This is most useful when
  30. combined with the B<-strparse> option.
  31. =item B<-noout>
  32. don't output the parsed version of the input file.
  33. =item B<-offset number>
  34. starting offset to begin parsing, default is start of file.
  35. =item B<-length number>
  36. number of bytes to parse, default is until end of file.
  37. =item B<-i>
  38. indents the output according to the "depth" of the structures.
  39. =item B<-oid filename>
  40. a file containing additional OBJECT IDENTIFIERs (OIDs). The format of this
  41. file is described in the NOTES section below.
  42. =item B<-strparse offset>
  43. parse the contents octets of the ASN.1 object starting at B<offset>. This
  44. option can be used multiple times to "drill down" into a nested structure.
  45. =item B<-genstr string>, B<-genconf file>
  46. generate encoded data based on B<string>, B<file> or both using
  47. L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> format. If B<file> only is
  48. present then the string is obtained from the default section using the name
  49. B<asn1>. The encoded data is passed through the ASN1 parser and printed out as
  50. though it came from a file, the contents can thus be examined and written to a
  51. file using the B<out> option.
  52. =back
  53. =head2 OUTPUT
  54. The output will typically contain lines like this:
  55. 0:d=0 hl=4 l= 681 cons: SEQUENCE
  56. .....
  57. 229:d=3 hl=3 l= 141 prim: BIT STRING
  58. 373:d=2 hl=3 l= 162 cons: cont [ 3 ]
  59. 376:d=3 hl=3 l= 159 cons: SEQUENCE
  60. 379:d=4 hl=2 l= 29 cons: SEQUENCE
  61. 381:d=5 hl=2 l= 3 prim: OBJECT :X509v3 Subject Key Identifier
  62. 386:d=5 hl=2 l= 22 prim: OCTET STRING
  63. 410:d=4 hl=2 l= 112 cons: SEQUENCE
  64. 412:d=5 hl=2 l= 3 prim: OBJECT :X509v3 Authority Key Identifier
  65. 417:d=5 hl=2 l= 105 prim: OCTET STRING
  66. 524:d=4 hl=2 l= 12 cons: SEQUENCE
  67. .....
  68. This example is part of a self signed certificate. Each line starts with the
  69. offset in decimal. B<d=XX> specifies the current depth. The depth is increased
  70. within the scope of any SET or SEQUENCE. B<hl=XX> gives the header length
  71. (tag and length octets) of the current type. B<l=XX> gives the length of
  72. the contents octets.
  73. The B<-i> option can be used to make the output more readable.
  74. Some knowledge of the ASN.1 structure is needed to interpret the output.
  75. In this example the BIT STRING at offset 229 is the certificate public key.
  76. The contents octets of this will contain the public key information. This can
  77. be examined using the option B<-strparse 229> to yield:
  78. 0:d=0 hl=3 l= 137 cons: SEQUENCE
  79. 3:d=1 hl=3 l= 129 prim: INTEGER :E5D21E1F5C8D208EA7A2166C7FAF9F6BDF2059669C60876DDB70840F1A5AAFA59699FE471F379F1DD6A487E7D5409AB6A88D4A9746E24B91D8CF55DB3521015460C8EDE44EE8A4189F7A7BE77D6CD3A9AF2696F486855CF58BF0EDF2B4068058C7A947F52548DDF7E15E96B385F86422BEA9064A3EE9E1158A56E4A6F47E5897
  80. 135:d=1 hl=2 l= 3 prim: INTEGER :010001
  81. =head1 NOTES
  82. If an OID is not part of OpenSSL's internal table it will be represented in
  83. numerical form (for example 1.2.3.4). The file passed to the B<-oid> option
  84. allows additional OIDs to be included. Each line consists of three columns,
  85. the first column is the OID in numerical format and should be followed by white
  86. space. The second column is the "short name" which is a single word followed
  87. by white space. The final column is the rest of the line and is the
  88. "long name". B<asn1parse> displays the long name. Example:
  89. C<1.2.3.4 shortName A long name>
  90. =head1 EXAMPLES
  91. Parse a file:
  92. openssl asn1parse -in file.pem
  93. Parse a DER file:
  94. openssl asn1parse -inform DER -in file.der
  95. Generate a simple UTF8String:
  96. openssl asn1parse -genstr 'UTF8:Hello World'
  97. Generate and write out a UTF8String, don't print parsed output:
  98. openssl asn1parse -genstr 'UTF8:Hello World' -noout -out utf8.der
  99. Generate using a config file:
  100. openssl asn1parse -genconf asn1.cnf -noout -out asn1.der
  101. Example config file:
  102. asn1=SEQUENCE:seq_sect
  103. [seq_sect]
  104. field1=BOOL:TRUE
  105. field2=EXP:0, UTF8:some random string
  106. =head1 BUGS
  107. There should be options to change the format of output lines. The output of some
  108. ASN.1 types is not well handled (if at all).
  109. =head1 SEE ALSO
  110. L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)>
  111. =cut