<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Encryption on D'Arcy Norman, PhD</title><link>https://darcynorman.net/tags/encryption/</link><description>Recent content in Encryption on D'Arcy Norman, PhD</description><generator>Hugo</generator><language>en-us</language><managingEditor>dnorman@me.com (D'Arcy Norman)</managingEditor><webMaster>dnorman@me.com (D'Arcy Norman)</webMaster><lastBuildDate>Wed, 18 Mar 2015 08:44:22 +0000</lastBuildDate><atom:link href="https://darcynorman.net/tags/encryption/index.xml" rel="self" type="application/rss+xml"/><item><title>https by default</title><link>https://darcynorman.net/2015/03/18/https-by-default/</link><pubDate>Wed, 18 Mar 2015 08:44:22 +0000</pubDate><author>dnorman@me.com (D'Arcy Norman)</author><guid>https://darcynorman.net/2015/03/18/https-by-default/</guid><description>&lt;p&gt;I&amp;rsquo;ve had an SSL certificate installed on my website for awhile now, but it only kicked in if someone manually typed in &lt;code&gt;HTTPS&lt;/code&gt; (which I&amp;rsquo;ve been using when I login to the site to do stuff). I&amp;rsquo;m trying to reduce ways in which my activities online expose privacy (for both myself and the 3 people who read my blog), so &lt;a href="http://www.dailydot.com/politics/federal-websites-https-secure-proposal/"&gt;it&amp;rsquo;s time&lt;/a&gt; to throw the switch for the default to be encrypted HTTPS SSL access to this site. I&amp;rsquo;d held off because I wasn&amp;rsquo;t entirely comfortable that my SSL certificate would be accepted by all browsers, but it seems to be working. I&amp;rsquo;ll be switching to the new &lt;a href="https://letsencrypt.org/2014/11/18/announcing-lets-encrypt.html"&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt; SSL/TLS system as soon as it&amp;rsquo;s up and running. Hopefully this summer.&lt;/p&gt;</description></item></channel></rss>