Upgrade chrome's OpenSSL to same version Android ships with.

openssl/doc/apps/asn1parse.pod

 =pod
 
 =head1 NAME
 
 asn1parse - ASN.1 parsing tool
 
 =head1 SYNOPSIS
 
 B<openssl> B<asn1parse>
 [B<-inform PEM|DER>]
@@ skipping 54 matching lines @@
 file is described in the NOTES section below.
 
 =item B<-strparse offset>
 
 parse the contents octets of the ASN.1 object starting at B<offset>. This
 option can be used multiple times to "drill down" into a nested structure.
 
 =item B<-genstr string>, B<-genconf file>
 
 generate encoded data based on B<string>, B<file> or both using
-ASN1_generate_nconf() format. If B<file> only is present then the string
-is obtained from the default section using the name B<asn1>. The encoded
-data is passed through the ASN1 parser and printed out as though it came
-from a file, the contents can thus be examined and written to a file
-using the B<out> option. 
+L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> format. If B<file> only is
+present then the string is obtained from the default section using the name
+B<asn1>. The encoded data is passed through the ASN1 parser and printed out as
+though it came from a file, the contents can thus be examined and written to a
+file using the B<out> option. 
 
 =back
 
 =head2 OUTPUT
 
 The output will typically contain lines like this:
 
   0:d=0  hl=4 l= 681 cons: SEQUENCE          
 
 .....
@@ skipping 71 matching lines @@
 
  field1=BOOL:TRUE
  field2=EXP:0, UTF8:some random string
 
 
 =head1 BUGS
 
 There should be options to change the format of output lines. The output of some
 ASN.1 types is not well handled (if at all).
 
+=head1 SEE ALSO
+
+L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)>
+
 =cut