Added -strictpem parameter to enable processing of PEM files with data prior to the BEGIN marker

1 files changed, 9 insertions, 1 deletions

diff --git a/doc/apps/asn1parse.pod b/doc/apps/asn1parse.pod
index f7bb926211..577d997630 100644
--- a/doc/apps/asn1parse.pod
+++ b/doc/apps/asn1parse.pod
@@ -18,6 +18,7 @@ B<openssl> B<asn1parse>
 [B<-strparse offset>]
 [B<-genstr string>]
 [B<-genconf file>]
+[B<-strictpem>]
 
 =head1 DESCRIPTION
 
@@ -78,6 +79,13 @@ 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. 
 
+=item B<-strictpem>
+
+If this option is used then B<-inform> will be ignored. Without this option any
+data in a PEM format input file will be treated as base64 encoded and processed
+whether it has the normal PEM BEGIN and END markers or not. This option will
+ignore any data prior to the start of the BEGIN marker in a PEM file.
+
 =back
 
 =head2 OUTPUT
@@ -88,7 +96,7 @@ The output will typically contain lines like this:
 
 .....
 
-  229:d=3  hl=3 l= 141 prim: BIT STRING        
+  229:d=3  hl=3 l= 141 prim: BIT STRING
   373:d=2  hl=3 l= 162 cons: cont [ 3 ]        
   376:d=3  hl=3 l= 159 cons: SEQUENCE          
   379:d=4  hl=2 l=  29 cons: SEQUENCE