Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I generate a p12 certificate with openssl as:
openssl pkcs12 -export -in myprivatecert.pem -nokeys -out mycert.p12
Even though I ask openssl to not export the private key, why does windows still require the private key password when installing the certificate.
I figure I am missing something.
The password is for the PKCS12 file itself, not for the private key. You can specify a blank password by adding “-password pass:” like this:
You will still be prompted by Windows for the password, but you can leave it empty, and the import will work fine.
If all you are importing on Windows is the certificate, without the key, they you can also use the DER format like this:
One benefit of this is that when you double-click this file on Windows, it recognizes the der extension, and you can view the certificate details just before importing. Also, there will be no password prompt.