<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tls on Evan Hoffman</title><link>https://evan.wtf/tags/tls/</link><description>Recent content in Tls on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Tue, 20 Sep 2011 14:06:38 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/tls/index.xml" rel="self" type="application/rss+xml"/><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>Relaying through Google Apps using Sendmail to bypass EC2 spam blockage</title><link>https://evan.wtf/2010/12/01/relaying-through-google-apps-using-sendmail-to-bypass-ec2-spam-blockage/</link><pubDate>Wed, 01 Dec 2010 14:48:06 +0000</pubDate><guid>https://evan.wtf/2010/12/01/relaying-through-google-apps-using-sendmail-to-bypass-ec2-spam-blockage/</guid><description>&lt;p&gt;Update 3 May 2011: I&amp;rsquo;ve subsequently modified our EC2 systems to &lt;a href="https://evan.wtf/2011/04/28/integrating-amazon-simple-email-service-with-postfix-for-smarthost-relaying/"&gt;relay SMTP mail through Amazon&amp;rsquo;s SES&lt;/a&gt; which doesn&amp;rsquo;t have the 500 messages per day limit that Google Apps does.&lt;/p&gt;&#10;&lt;p&gt;A few months ago I moved a site into EC2. I didn&amp;rsquo;t want to move the existing IMAP server (ugh) so I moved the email to Google Apps. There are only about 10 mailboxes so we went with &amp;ldquo;Standard&amp;rdquo; edition (free). Once we completed the move to EC2 we discovered that emails from our webserver were bouncing due to our EC2 IP address being listed in a spam RBL. This sucked, so I looked into relaying the mail from the EC2 webserver through our Google Apps account. Fortunately this turned out to be pretty easy.&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>