This is a feature not a bug ;-) This is actually by design, in that asn1parse is capable of handing arbitrary base64 encoded data (without the PEM BEGIN and END markers). As such it's not quite as simple as just modifying the behaviour to work in the way that you have described (since this would break the capability to read plain base64 data).
However it does seem reasonable to be able to process PEM files with data prior to the BEGIN markers, so I have added a new option "-strictpem" to cater for this scenario: http://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=6b5c1d940b5a653a24b91d3c52bca935399b713c Matt ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
