Hi, There appears to be a bug in the "openssl pkcs8" command under Win32 1.0.0a. I am using Win32 binaries from (http://www.slproweb.com/products/Win32OpenSSL.html).
The command "openssl pkcs8 -in \test.pem" should accept a pkcs#8 file and output traditional format. With v0.9.8o the above command produces the expected output; which has the header "-----BEGIN RSA PRIVATE KEY-----". The gnuwin32 compilation of 0.9.8h also produces the expected output. However, under OpenSSL 1.0.1a the same command produces PKCS#8 output, which has the header "-----BEGIN PRIVATE KEY-----". There doesn't appear to be any option to produce traditional format; which is required for compatibility. Joe Sebastian [email protected] SAP GRC - Security & Portals office +1 708-450-2872 mobile +1 708-220-7135 [cid:[email protected]]<http://www.linkedin.com/in/joesebastian>
|
Hi, There appears to be a bug in the “openssl pkcs8”
command under Win32 1.0.0a. I am using Win32 binaries from (http://www.slproweb.com/products/Win32OpenSSL.html).
The command "openssl pkcs8 -in \test.pem" should
accept a pkcs#8 file and output traditional format. With v0.9.8o the above command produces the expected output;
which has the header "-----BEGIN RSA PRIVATE KEY-----". The gnuwin32
compilation of 0.9.8h also produces the expected output. However, under OpenSSL 1.0.1a the same command produces
PKCS#8 output, which has the header "-----BEGIN PRIVATE KEY-----". There doesn’t appear to be any option to produce
traditional format; which is required for compatibility. Joe Sebastian [email protected] |
<<inline: image001.gif>>
