I hit a bug when inputting an x509 certificate into openssl. My CA is Entrust.net, and they have some certificates for download that have no line endings in the encoding. This causes openssl parser to fail when it tries to read the certificate, even thought the certificate is valid. Here is the response from Entrust.net:
I checked into this formatting question some more for you. The Certificate > PEM file format contains the encoded text contents. White > space/tabs/newlines etc are not (supposed to be) significant. > > Most SSL tools and utilities should be able to handle the certificate PEM > file no matter the white spacing. > > However, some tools and utilities (as you observed) have different > requirements for the formatting when reading PEM format file. > For now the workaround will be to switch between formatting as needed. > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
