<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Openssl on Evan Hoffman</title><link>https://evan.wtf/tags/openssl/</link><description>Recent content in Openssl on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Tue, 14 Oct 2014 12:01:49 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/openssl/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing a new SSL certificate in your ELB via CLI</title><link>https://evan.wtf/2014/10/14/installing-a-new-ssl-certificate-in-your-elb-via-cli/</link><pubDate>Tue, 14 Oct 2014 12:01:49 +0000</pubDate><guid>https://evan.wtf/2014/10/14/installing-a-new-ssl-certificate-in-your-elb-via-cli/</guid><description>&lt;p&gt;For future me:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Create the key and CSR:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;$ openssl req -out wildcard.site.com.csr -new -newkey rsa:2048 -nodes -keyout wildcard.site.com.key&#10;&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Upload the CSR to your SSL vendor (in this case, DigiCert) and obtain the signed SSL certificate.&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Create a PEM-encoded version of the signing key. This is required for AWS/IAM certs. To check if your key is already PEM-encoded, just &amp;ldquo;head -1 site.key&amp;rdquo;. If the first line says &amp;ldquo;&amp;mdash;&amp;ndash;BEGIN PRIVATE KEY&amp;mdash;&amp;ndash;&amp;rdquo; then it&amp;rsquo;s NOT PEM-encoded. The first line should be &amp;ldquo;&amp;mdash;&amp;ndash;BEGIN RSA PRIVATE KEY&amp;mdash;&amp;ndash;&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Making sure SSLv2 is disabled in Apache (and Nginx)</title><link>https://evan.wtf/2011/09/20/making-sure-sslv2-is-disabled-in-apache/</link><pubDate>Tue, 20 Sep 2011 14:06:38 +0000</pubDate><guid>https://evan.wtf/2011/09/20/making-sure-sslv2-is-disabled-in-apache/</guid><description>&lt;p&gt;&lt;strong&gt;Edit Jan 24, 2012:&lt;/strong&gt; Deleted all the crap from this story and just left the recommended Apache and Nginx SSL cipher suites for maximum security without SSLv2 and without BEAST vulnerability (at least according to Qualys).&#10;&lt;strong&gt;Apache httpd&lt;/strong&gt;&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;SSLProtocol -ALL +SSLv3 +TLSv1&#10;SSLCipherSuite ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM;&#10;SSLHonorCipherOrder on&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;strong&gt;nginx&lt;/strong&gt;&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;ssl_protocols SSLv3 TLSv1;&#10; ssl_ciphers ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM;&#10; ssl_prefer_server_ciphers on;&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Source:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://community.qualys.com/blogs/securitylabs/2011/10/17/mitigating-the-beast-attack-on-tls"&gt;Qualys&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.ssllabs.com/ssldb/"&gt;SSL checker&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;&lt;a href="http://affiliate.godaddy.com/redirect/5F43C3ECBA841ACFC3859F4F4E6CA7DA64C271385B2D61A3AD6F3CCE83EB1DD8235E60DCD7D63BCD92E2429E79A75FAC"&gt;&lt;img src="http://affiliate.godaddy.com/ads/5F43C3ECBA841ACFC3859F4F4E6CA7DA64C271385B2D61A3AD6F3CCE83EB1DD8235E60DCD7D63BCD92E2429E79A75FAC" alt="Go Daddy $12.99 SSL Sale!"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Wasted time with Exchange 2010, SquirrelMail, and IMAP-SSL</title><link>https://evan.wtf/2010/11/30/wasted-time-with-exchange-2010-squirrelmail-and-imap-ssl/</link><pubDate>Tue, 30 Nov 2010 17:32:11 +0000</pubDate><guid>https://evan.wtf/2010/11/30/wasted-time-with-exchange-2010-squirrelmail-and-imap-ssl/</guid><description>&lt;p&gt;I&amp;rsquo;m setting up SquirrelMail to point to my Exchange 2010 server via IMAP (don&amp;rsquo;t ask) and couldn&amp;rsquo;t get SM to talk to Exchange on port 993 (imaps). Even though the servers on the same subnet, any time passwords are being sent over the network I like to opt for SSL. I found a couple of sites suggesting that the problem was that there was no SSL certificate installed, but I knew for a fact there was a valid certificate because I could get to &lt;a href="https://webmail.example.com/"&gt;https://webmail.example.com/&lt;/a&gt; for OWA.&lt;/p&gt;</description></item></channel></rss>