From verify documentation: If a certificate is found which is its own issuer it is assumed to be the root CA. In other words, root CA needs to be self signed for verify to work. This is why your second command didn’t work. Try this instead: openssl verify -CAfile RootCert.pem -untrusted Intermediate.pem UserCert.pem It will … Read more
I had the same problem (openssl) and this worked for me on Ubuntu 14.04.1 LTS. The solution is the same up to Ubuntu 18.04 (tested). sudo apt-get install libssl-dev
See https://polarssl.org/kb/cryptography/asn1-key-structures-in-der-and-pem (search the page for “BEGIN RSA PRIVATE KEY”) (archive link for posterity, just in case). BEGIN RSA PRIVATE KEY is PKCS#1 and is just an RSA key. It is essentially just the key object from PKCS#8, but without the version or algorithm identifier in front. BEGIN PRIVATE KEY is PKCS#8 and indicates that … Read more
Try: openssl pkcs12 -in path.p12 -out newfile.crt.pem -clcerts -nokeys openssl pkcs12 -in path.p12 -out newfile.key.pem -nocerts -nodes After that you have: certificate in newfile.crt.pem private key in newfile.key.pem To put the certificate and key in the same file without a password, use the following, as an empty password will cause the key to not be … Read more
In practice, the most common reason for this happening seems to be that the .rnd file in your home directory is owned by root rather than your account. The quick fix: sudo rm ~/.rnd For more information, here’s the entry from the OpenSSL FAQ: Sometimes the openssl command line utility does not abort with a … Read more
openssl genrsa -out mykey.pem 1024 will actually produce a public – private key pair. The pair is stored in the generated mykey.pem file. openssl rsa -in mykey.pem -pubout > mykey.pub will extract the public key and print that out. Here is a link to a page that describes this better. EDIT: Check the examples section … Read more