<?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; SSL</title> <atom:link href="http://newpush.com/tag/ssl/feed/" rel="self" type="application/rss+xml" /><link>http://newpush.com</link> <description>Server Hosting, Data Warehouse Hosting, Collaboration</description> <lastBuildDate>Wed, 23 May 2012 03:47:03 +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>Domino 8.5 SSL Key Import Into Keyring File</title><link>http://newpush.com/2011/04/domino-8-5-ssl-key-import-into-keyring-file/</link> <comments>http://newpush.com/2011/04/domino-8-5-ssl-key-import-into-keyring-file/#comments</comments> <pubDate>Sat, 09 Apr 2011 23:40:05 +0000</pubDate> <dc:creator>Bill</dc:creator> <category><![CDATA[AIX]]></category> <category><![CDATA[Cloud Computing]]></category> <category><![CDATA[Collaboration]]></category> <category><![CDATA[Dedicated Servers]]></category> <category><![CDATA[Domino]]></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[email]]></category> <category><![CDATA[Keyring]]></category> <category><![CDATA[Lotus]]></category> <category><![CDATA[Secure Certificates]]></category> <category><![CDATA[SSL]]></category> <category><![CDATA[TLS]]></category><guid isPermaLink="false">http://newpush.com/?p=1073</guid> <description><![CDATA[Domino Server SSL Key Import By default, the SSL key order process in the Domino Administrator assumes that only single domain certificates are used. Hence, when you have a multi domain UCC or a wildcard certificate, it has to be &#8230; <a href="http://newpush.com/2011/04/domino-8-5-ssl-key-import-into-keyring-file/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<h1>Domino Server SSL Key Import</h1><p>By default, the SSL key order process in the Domino Administrator assumes that only single domain certificates are used.  Hence, when you have a multi domain UCC or a wildcard certificate, it has to be loaded into the keyring (a.k.a. kyr file) outside of the Domino Administrator.</p><p>The basic overview of the process is this:</p><ul><li>Create a <code>kyr</code> (keyring) file to hold the keys.</li><li>Create a <code>p12</code> (PKCS#12) file with the certificate that needs to be added to the keyring.</li><li>Add the <code>p12</code> (PKCS#12) file to the keyring.</li><li>Install the new keyring on the Domino Servers (mail, traveler, sametime, Quickr)</li></ul><h2>Domino Server PKCS#12 key generation and import</h2><h3>Create PKCS#12 from SSL KEY and CRT files</h3><p>For this step I recommend to be on the Linux or AIX with openssl installed.  Assuming that you have the certificate key, the CA issued certificate, and the certificate chains all in the same directory, you can run the following command to generate the <code>p12</code> file:<br /> <code><br /> openssl pkcs12 -export \<br /> -in certificate-from-CA.crt \<br /> -inkey certificate-key-file.key \<br /> -certfile root-ca-bundle.crt \<br /> -out certificate-in-pkcs12-format.p12<br /> </code></p><h3>Add PKCS#12 to Domino Server Kyr Keyring File</h3><p>For this step I recommend to be on the sametime server under Linux or AIX.  In theory, this should work, but in practice, I found that the version 7 of the <code>gsk</code> tools doesn&#8217;t seem to be able to open <code>kyr</code> files.  So you may need to skip ahead to the legacy Windows XP method, unless you can find the <code>gsk5bas</code> package on one of your older install media.<br /> <code><br /> rpm -Uvh ${SAMETIME_CD_PATH}/SametimeEntryServer/GSKit/Linux/gsk7bas-7.0-4.28.i386.rpm<br /> vi /opt/ibm/lotus/notes/latest/linux/ibm-jre/jre/lib/security/java.security<br /> </code><br /> Add last provider to list:<br /> <code><br /> security.provider.1=com.ibm.jsse2.IBMJSSEProvider2<br /> security.provider.2=com.ibm.crypto.provider.IBMJCE<br /> security.provider.3=com.ibm.security.jgss.IBMJGSSProvider<br /> security.provider.4=com.ibm.security.cert.IBMCertPath<br /> security.provider.5=com.ibm.security.sasl.IBMSASL<br /> security.provider.6=com.ibm.spi.IBMCMSProvider<br /> </code><br /> remove conflicting jar file:<br /> <code><br /> mv /opt/ibm/lotus/notes/latest/linux/ibm-jre/jre/lib/ext/gskikm.jar /opt/ibm/lotus/notes/latest/linux/ibm-jre/jre/lib/ext/gskikm.removedjar-<br /> </code><br /> set environment:<br /> <code><br /> set JAVA_HOME<br /> JAVA_HOME=/opt/ibm/lotus/notes/latest/linux/ibm-jre/jre export JAVA_HOME<br /> </code></p><h3>Domino Server Required Utilities for SSL Key Import (legacy Windows XP method)</h3><ul><li>Download and install <a href="ftp://ftp.software.ibm.com/software/lotus/tools/Domino/gsk5-ikeyman.zip">IKEYMAN</a>.</li><li>Open the kyr file in gsk5.</li><li>Import the p12 cert.</li><li>Save the new kyr file.</li></ul><h3>Domino Server SSL Key Management References</h3><ul><li>http://www.redbooks.ibm.com/redpapers/pdfs/redp0046.pdf</li><li>http://www.turtleweb.com/turtleblog.nsf/dx/11022009232215GDAVGR.htm?opendocument&#038;comments</li><li>http://www.deadspace.de/?p=294</li><li>ftp://ftp.software.ibm.com/software/webserver/appserv/library/v61/ihs/GSK7c_SSL_Ikm_Guide.pdf</li><li>https://support.quovadisglobal.com/KB/a93/how-do-i-install-my-digital-certificate-into-lotus-notes.aspx</li><li>http://replay.waybackmachine.org/20081121002554/http://www.justinclarke.com/archives/2005/08/sending_smime_e.html</li><li>http://www.eulerhermes.com/en/documents/secure-email/ehcica_howto_import_lotus_notes_en.pdf/ehcica_howto_import_lotus_notes_en.pdf</li><li>http://publib.boulder.ibm.com/infocenter/sametime/v8r0/index.jsp?topic=/com.ibm.help.sametime.802.doc/Entry/st_adm_security_ssl_ikey_lin_t.html</li></ul><p>For more information about <b>Domino Server</b> solutions, visit our <a href="http://newpush.com/collaboration">collaboration</a> section.</p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2011/04/domino-8-5-ssl-key-import-into-keyring-file/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Verifying SSL Certificates</title><link>http://newpush.com/2010/12/verifying-ssl-certificates/</link> <comments>http://newpush.com/2010/12/verifying-ssl-certificates/#comments</comments> <pubDate>Fri, 31 Dec 2010 00:53:26 +0000</pubDate> <dc:creator>Pete</dc:creator> <category><![CDATA[AIX]]></category> <category><![CDATA[Cloud Computing]]></category> <category><![CDATA[Dedicated Servers]]></category> <category><![CDATA[Hosting Support]]></category> <category><![CDATA[Java]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac OS X]]></category> <category><![CDATA[Managed Hosting]]></category> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[OpenSSL]]></category> <category><![CDATA[SSL]]></category><guid isPermaLink="false">http://newpush.com/?p=915</guid> <description><![CDATA[Problem You have a few SSL cert files on your server, but you are not sure which one is the newest, or the right cert to use. Solution Look at the contents of a CSR openssl req -noout -text -in &#8230; <a href="http://newpush.com/2010/12/verifying-ssl-certificates/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<h4>Problem</h4><p>You have a few SSL cert files on your server, but you are not sure which one is the newest, or the right cert to use.</p><h4>Solution</h4><h5>Look at the contents of a CSR</h5><p><code><br /> openssl req -noout -text -in [domain_name].csr<br /> </code><br /> Where <code>[domain_name].csr</code> is the name of the CSR file.</p><h5>Look at the contents of a certificate</h5><p><code><br /> openssl x509 -noout -text -in [domain_name].crt<br /> </code></p><h5>Look at the MD5 fingerprint of a certificate</h5><p><code><br /> openssl x509 -fingerprint -noout -in [domain_name].crt<br /> </code></p><h5>Check the private key, the CSR, and the signed cert</h5><p>To check that the private key, the CSR, and the signed cert belong to the same set, you need to compare the MD5 outputs:<br /> <code><br /> openssl rsa -noout -modulus -in [domain_name].key |openssl md5<br /> openssl req -noout -modulus -in [domain_name].csr |openssl md5<br /> openssl x509 -noout -modulus -in [domain_name].crt |openssl md5<br /> </code></p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2010/12/verifying-ssl-certificates/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> <item><title>Do you need a secure certificate (SSL/HTTPS) for your site?</title><link>http://newpush.com/2006/11/do-you-need-a-secure-certificate-sslhttps-for-your-site/</link> <comments>http://newpush.com/2006/11/do-you-need-a-secure-certificate-sslhttps-for-your-site/#comments</comments> <pubDate>Sun, 12 Nov 2006 08:51:46 +0000</pubDate> <dc:creator>Domonkos</dc:creator> <category><![CDATA[Cloud Computing]]></category> <category><![CDATA[Dedicated Servers]]></category> <category><![CDATA[Hosting Support]]></category> <category><![CDATA[Managed Hosting]]></category> <category><![CDATA[HTTPS]]></category> <category><![CDATA[Secure Certificates]]></category> <category><![CDATA[SSL]]></category><guid isPermaLink="false">http://newpush.com/?p=1541</guid> <description><![CDATA[A secure certificate (aka SSL cert) allows a web site to secure the connection between the web server and the visitor. That allows protection of the users privacy and the confidentiality of the data. A secure certificate technically does the &#8230; <a href="http://newpush.com/2006/11/do-you-need-a-secure-certificate-sslhttps-for-your-site/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p>A secure certificate (aka SSL cert) allows a web site to secure the connection between the web server and the visitor. That allows protection of the users privacy and the confidentiality of the data. A secure certificate technically does the following two things:</p><ul><li>Guarantee that the website you are looking at is truely the website you are expecting to look at (to avoid &#8220;man in the middle&#8221; attacks)</li><li>Encrypt the connection so that 3rd parties that are trying to &#8220;sniff&#8221; the data can not discover the contents</li></ul><p>In order to begin timely processing of a secure certificate order we will need the following documentation:</p><p>Proof of Organization, which can be any of the following:</p><ul><li>DUNS number (Dun and Bradstreet)</li><li>Articles of Incorporation or Business License</li><li>Doing Business As (DBA) registration</li><li>Sole Proprietorship documentation</li></ul><p>Please note: Company name and addresses listed on these documents will need to match the current domain registration company name and address. You can look up your domain registration information here: <a href="http://opensrs.org/cgi-bin/whois.cgi" target="_blank">http://opensrs.org/cgi-bin/whois.cgi</a></p><p>Please email, <a href="mailto:orders@thenewpush.com">orders@thenewpush.com</a>, or fax, 1-720-294-0933, the documents to us.</p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2006/11/do-you-need-a-secure-certificate-sslhttps-for-your-site/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Served from: newpush.com @ 2012-05-23 05:59:50 by W3 Total Cache -->
