<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" ><channel><title>NewPush &#187; Certificates</title> <atom:link href="http://newpush.com/tag/certificates/feed/" rel="self" type="application/rss+xml" /><link>http://newpush.com</link> <description>Server Hosting, Data Warehouse Hosting, Collaboration</description> <lastBuildDate>Fri, 20 Apr 2012 10:25:44 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>Creating an easy to deploy SSL certificate in PEM format</title><link>http://newpush.com/2011/11/creating-an-easy-to-deploy-ssl-certificate-in-pem-format/</link> <comments>http://newpush.com/2011/11/creating-an-easy-to-deploy-ssl-certificate-in-pem-format/#comments</comments> <pubDate>Mon, 07 Nov 2011 17:03:02 +0000</pubDate> <dc:creator>Balazs</dc:creator> <category><![CDATA[AIX]]></category> <category><![CDATA[Cloud Computing]]></category> <category><![CDATA[Dedicated Servers]]></category> <category><![CDATA[Hosting Support]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac OS X]]></category> <category><![CDATA[Managed Hosting]]></category> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[Apache]]></category> <category><![CDATA[Certificate Chain]]></category> <category><![CDATA[Certificates]]></category> <category><![CDATA[PEM]]></category> <category><![CDATA[Secure Certificates]]></category> <category><![CDATA[SSL]]></category><guid isPermaLink="false">http://newpush.com/?p=1379</guid> <description><![CDATA[When ordering a secure certificate, most often one has to deal with the following files: certificate key file (aka private key): .key certificate request file: .csr primary certificate file (issued by the CA): .crt certificate chain (aka intermediate certificate, or &#8230; <a href="http://newpush.com/2011/11/creating-an-easy-to-deploy-ssl-certificate-in-pem-format/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p>When ordering a secure certificate, most often one has to deal with the following files:</p><ul><li>certificate key file (aka private key): .key</li><li>certificate request file: .csr</li><li>primary certificate file (issued by the CA): .crt</li><li>certificate chain (aka intermediate certificate, or sf bundle): sf_bundle.crt</li></ul><p>As a result, when deploying to a web server, it is necessary to configure 3 files: the key, the cert, and the trust chain.  However, a little known fact is that these can be combined in a &#8220;pem&#8221; file that holds all three.  One may even include the trusted root certificate optionally.  Here is how:</p><ul><li>download your certificates (your_domain_name.crt) from your <a href="http://newpush.com/portal/">NewPush Customer Portal</a>.</li><li>paste the entire body of each certificate one by one into one text file in the following order:<ul><li><strong>domain.key</strong></li><li><strong>domain.crt</strong></li><li><strong>sf_bundle.crt</strong></li></ul><p>Make sure to include the beginning and end tags on each certificate. The result should look like this:<br /> <code><br /> -----BEGIN RSA PRIVATE KEY-----<br /> ...<br /> -----END RSA PRIVATE KEY-----<br /> -----BEGIN CERTIFICATE-----<br /> ...<br /> -----END CERTIFICATE-----<br /> -----BEGIN CERTIFICATE-----<br /> ...<br /> -----END CERTIFICATE-----<br /> -----BEGIN CERTIFICATE-----<br /> ...<br /> -----END CERTIFICATE-----<br /> -----BEGIN CERTIFICATE-----<br /> ...<br /> -----END CERTIFICATE-----<br /> </code></ul><p>The number of<br /> <code><br /> -----BEGIN CERTIFICATE-----<br /> ...<br /> -----END CERTIFICATE-----<br /> </code><br /> sections will depend of the length of the certificate trust chain.</p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2011/11/creating-an-easy-to-deploy-ssl-certificate-in-pem-format/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to add a secure cert to IIS on Windows</title><link>http://newpush.com/2009/05/how-to-add-a-secure-cert-to-iis-on-windows/</link> <comments>http://newpush.com/2009/05/how-to-add-a-secure-cert-to-iis-on-windows/#comments</comments> <pubDate>Sun, 31 May 2009 15:30:36 +0000</pubDate> <dc:creator>Balazs</dc:creator> <category><![CDATA[Windows]]></category> <category><![CDATA[Certificates]]></category> <category><![CDATA[SSL]]></category><guid isPermaLink="false">http://www.wdream.com/?p=293</guid> <description><![CDATA[To add an SSL cert to IIS 5 on Windows, you need two separate steps: Create a p12 (pkcs12) cert file: cat server.key server.crt &#62; server.pem openssl pkcs12 -export -in server.pem -out server.p12 -name "server" Import the p12 file into &#8230; <a href="http://newpush.com/2009/05/how-to-add-a-secure-cert-to-iis-on-windows/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p><span class="grey">To add an SSL cert to IIS 5 on Windows, you need two separate steps:</p><ol><li>Create a p12 (pkcs12) cert file:</li><pre>cat server.key server.crt &gt; server.pem
openssl pkcs12 -export -in server.pem -out server.p12 -name "server"</pre><li>Import the p12 file into IIS:</li><pre>Start-&gt;Run-&gt;mmc
Ctrl+M
Add...
Certificates
Computer Account
Finish
Close
OK
Open "Certificates (Local Computer)" tree
Right click Certificates
All Tasks-&gt;Import...
Browse to .p12 cert
Next
Next
Next
Finish</pre><li>Select cert for site</li><pre>Open IIS Admin
Select properties of website
Select Directory Security Tab
Server Certificate...
Next
Assign existing cert
Next
Select Cert
Next
Next
Finish
Web Site tab
SSL Port 443
Apply
OK</pre></ol><p></span></p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2009/05/how-to-add-a-secure-cert-to-iis-on-windows/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to remove a passphrase from an SSL cert key</title><link>http://newpush.com/2009/05/how-to-remove-a-passphrase-from-an-ssl-cert-key/</link> <comments>http://newpush.com/2009/05/how-to-remove-a-passphrase-from-an-ssl-cert-key/#comments</comments> <pubDate>Sun, 31 May 2009 14:10:01 +0000</pubDate> <dc:creator>Balazs</dc:creator> <category><![CDATA[Dedicated Servers]]></category> <category><![CDATA[Hosting Support]]></category> <category><![CDATA[Managed Hosting]]></category> <category><![CDATA[Certificates]]></category> <category><![CDATA[OpenSSL]]></category> <category><![CDATA[SSL]]></category><guid isPermaLink="false">http://www.wdream.com/?p=232</guid> <description><![CDATA[Here are the steps to remove a pass phrase from a cert key. This solution was originally discovered on the modssl website: cp server.key server.key.org openssl rsa -in server.key.org -out server.key Make sure the key is readable by root only, &#8230; <a href="http://newpush.com/2009/05/how-to-remove-a-passphrase-from-an-ssl-cert-key/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p><span class="grey">Here are the steps to remove a pass phrase from a cert key.  This solution was originally discovered on the <a href="http://www.modssl.org/docs/2.8/ssl%5C_faq.html%5C#ToC31">modssl</a> website:</p><pre>cp server.key server.key.org
openssl rsa -in server.key.org -out server.key</pre><p>Make sure the key is readable by root only,</p><pre>chmod 400 server.key</pre><p></span></p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2009/05/how-to-remove-a-passphrase-from-an-ssl-cert-key/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Served from: newpush.com @ 2012-05-22 11:04:57 by W3 Total Cache -->
