Hello,
> > This file is not PEM format, after exporting certificate (under Windows)
> > from this file to PEM encoded certificate this looks redable under
> > Linux.
> >   
> I'm afraid I don't understand what you mean. The file I sent was a *.crt
> file. What am I to do to get the file to work? Here's the *.pem file, if
> that helps:
In your first mail with certificate you send base64 encoded X509
certificate, this is not PEM format and this format must be converted
to PEM.
Lets say that this data was saved to file cert.b64, then you may
display this data with command:

$ openssl base64 -d -in cert.b64 | openssl x509 -inform der -text -noout

and you may convert this file to PEM format with command:

$ openssl base64 -d -in cert.b64 | openssl x509 -inform der > cert.pem

and then you may display this PEM file with:

$ openssl x509 -in cert.pem -text -noout

In your second mail you send base64 encoded private key.
Of course this is only acceptable if this is only test key,
from now this key was "compromised" and should be used only
for test purpose which means that for production environment
you should generated new key and request new certificate.
Againg, lets say that this key was saved to file key.b64, then you may
display this key with command:

$ openssl base64 -d -in key.b64 | openssl rsa -inform der -text -noout

and you may convert this key to PEM format with command:

$ openssl base64 -d -in key.b64 | openssl rsa -inform der > key.pem

end then you may display this PEM key with:

$ openssl rsa -in key.pem -text -noout

Again, this files was DER files with base64 encoding, PEM files
have additional header files.

Best regards,
-- 
Marek Marcola <[EMAIL PROTECTED]>

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to