Skip to main content

From PFX to PEM

If you ever find yourself in the situation when you need to extract the certificate and the private key from the PFX file you might be somewhat disoriented at first, especially if your experience is limited to Windows systems. Do not despair, it is very easy to do.  

One possible scenario - you have requested and processed the original certificate using IIS, then exported certificate with the private key, either to be stored in the safe place as a backup or to be imported into other servers or devices (typical in case of say wildcard certificates). Then, when you try to import it into a Linux/Apache based appliance, you find out that it requires a slightly different format (a certificate file and a private key file):

First, you would need to get a hold of an OpenSSL toolkit, visit OpenSSL Project website or download Windows installer hereOnce you have installed OpenSSL and have your PFX file handy, you can run the following commands to extract the private key and the certificate into two separate files:

openssl.exe pkcs12 -in XYZ.pfx -nocerts -out XYZprivateKey.pem
openssl.exe pkcs12 -in XYZ.pfx -clcerts -nokeys -out XYZpublicCert.cer

That's it. You can now import them.


  1. I just wanted to say this is an elegantly composed article as we have seen here.Professional swiss work Certificate Generation Tool I got some knowledge from your article and also it is a significant article for us. Thanks for sharing an article like this.

  2. Further consideration is required to make sure playing coverage, industry practices and public well being measures extra effectively cut back playing harm in up to date settings. In particular, the proliferation of inducements and the poor pricing of 점보카지노 complex bets corresponding to multi-bets, and their outsized attraction to players with issues, must be a key area of focus. These incentivised bets goal problem players with poor odds, whereas profitable gamblers are banned from play by online betting suppliers. This mixture is clearly in opposition to customers’ reasonable expectations for fair-play in betting.


Post a Comment

Popular posts from this blog

Mail-enabled security groups in Office 365

Another update (11/19/2013):  further evolution of Office 365 services makes creation of distribution and security groups even easier, plus there's now an option of creating a dynamic distribution group (click here for more information):    Update (08/06/2012): a clear sign of Office 365 evolving along the same lines as other agile cloud services - small incremental features and minor new functionality are being delivered almost continuously and, unlike important major service updates,  without much fanfare. For example, there's no need to resort to using PowerShell to setup mail-enabled security groups anymore, it can now be done at creation using management portal:       Those managing Office 365 ( O365 ) tenant via the Microsoft Online Services Portal  ( MOS Portal ) interface would notice that there are two distinct group entities: Security Groups: can be created via MOS Portal (main portal page>Management>Security Groups) and used for assigning

Drumbeat - Sales and Technical Resources for Office 365

​ Drumbeat - provides information as well as technical and sales resources for Office 365. From partnering with Microsoft, to building up your sales and technical readiness, to adopting proven methodologies for successful deployment - you will find lots of good information and many helpful links there. Here's a quick sample of topics covered: The Customer Decision Framework is Microsoft's selling methodology designed to help partners sell Office 365 to their customers. Office 365 FastTrack is Microsoft's new, 3-step pilot and deployment methodology designed so customers experience service value early in the sales cycle with a smooth path to advance from a pilot to deployment.

UAG 2010, SP4

Unified Access Gateway (UAG) 2010 Service Pack 4 (SP4) has been out for a while. Another much anticipated update which brings support for  Windows 8.1, IE11, etc. Download the Service Pack  here Review release notes  here Read through the installation instructions here After performing the upgrade test UAG functionality from the client side, on a number of occasions the following error has been reported - "Forbidden Directory, Listing Denied Error code 403.14". If you find yourself among the unlucky few, read through the following post ; which applies, even though it references a different update. Here are the steps outlined in the post with a minor modification (steps 7-8): Open Forefront UAG management on the UAG server Open/Explore the Trunks under the HTTP and/or HTTPS connections Right click each Trunk and select Disable Save and Activate the UAG configuration Right Click the trunks again and select enable Save and Activate the Configuration again Open the