A PFX file is a certificate in PKCS#12 format. It contains the SSL certificate (public keys) and the corresponding private keys.<\/p>\n
Most of the Certificate Authorities will not issue certificates with the private key. They just issue and share the certificates in .cer, .crt, and .p7b formats which don’t have the private key in most of the cases.<\/p>\n
But, sometimes our application needs the certificate in .pfx format.<\/p>\n
Now, we have a .cer certificate in our hand, but we need a .pfx certificate to deploy. And, we can’t convert the .cer certificate to .pfx without the private key.<\/p>\n
This problem has created confusion in most people and may create delays in the certificate deployment\/renewal process. This topic provides instructions on how to convert the .pfx file to .crt and .key files.<\/p>\n
The certificate is, nominally, a container for the public key. It includes the public key, the server name, some extra information about the server, and a signature computed by a certification authority (CA). When the server sends its public key to a client, it actually sends its certificate, with a few other certificates (the certificate which contains the public key of the CA which signed its certificate, and the certificate for the CA which signed the CA’s certificate, and so on). Certificates are intrinsically public objects.<\/p>\n
A .pfx file is a PKCS#12 archive: a bag that can contain a lot of objects with optional password protection; but, usually, a PKCS#12 archive contains a certificate (possibly with its assorted set of CA certificates) and the corresponding private key.<\/p>\n
The PFX file is always password protected because it contains a private key. When creating a PFX, choose a password responsibly, as it can protect us from misuse of the certificate.<\/p>\n
An attacker would be pleased if the password to the stolen PFX file was “12345” – he could start using the certificate all the time immediately.<\/p>\n
OpenSSL is a library (program) available on any Unix operating system. If we have a Linux server or work on Linux, then OpenSSL is definitely among the available programs (in repository).<\/p>\n
In OpenSSL, separately stored keys must be used in a single PFX (PKCS#12) file. So join existing keys to PFX:<\/p>\n
When we enter the password protecting the certificate, the output.pfx file will be created in the directory (where we are located).<\/p>\n
<\/p>\n
Run the following command to extract the private key:<\/p>\n
We will be prompted to type the import password. Type the password that we used to protect our keypair when we created the .pfx file.<\/p>\n
We will be prompted again to provide a new password to protect the .key file that we are creating. Store the password to our key file in a secure place to avoid misuse.<\/p>\n
<\/p>\n
<\/p>\n
Run the following command to extract the certificate:<\/p>\n
Run the following command to decrypt the private key:<\/p>\n
Type the password that we created to protect the private key file in the previous step.<\/p>\n
Now we have the private key and certificate now.<\/p>\n
Summary:<\/p>\n
A PFX file is a certificate in PKCS#12 format. PKCS#12 is a standard for a container that can hold an X509 client certificate and the corresponding private keys, as well as (optionally) the X509 certificates of the CAs that signed the X509 client certificate(s).<\/p>\n","protected":false},"excerpt":{"rendered":"
A PFX file is a certificate in PKCS#12 format. It contains the SSL certificate (public keys) and the corresponding private keys. Most of the Certificate Authorities will not issue certificates with the private key. They just issue and share the certificates in .cer, .crt, and .p7b formats which don’t have the private key in most …<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"disable-in-feed":false,"article-schema-type":"","disable-critical-css":false,"footnotes":""},"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/posts\/210"}],"collection":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/comments?post=210"}],"version-history":[{"count":0,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/posts\/210\/revisions"}],"wp:attachment":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/media?parent=210"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/categories?post=210"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/tags?post=210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}