"Visionary Website Creations, Inc." wrote:
>
> >
> >What does this alleged certificate look like? Can you read it with
> >
> >openssl x509 -in cert.pem
> >
> >or does it give a similar error? Can you include the certificate file?
> >It doesn't contain anything confidential and it may be packaged in an
> >unusual way which needs converting.
> >
>
> It looks ok to me:
>
> ns1:/usr/local/ssl/bin # ./openssl x509 -in ../certs/probrasive.com.cert
Hmmm seems OK to me too. Is that the only certificate in the file?
I suppose it is possible that some other certificate it attempts to read
in somewhere is corrupt: check the trusted file or directory to see if
anything is wrong there.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
