﻿<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text" xml:lang="en">Encryption</title>
  <link type="application/atom+xml" href="https://d.moonfire.us/tags/encryption/atom.xml" rel="self" />
  <link type="text/html" href="https://d.moonfire.us/tags/encryption/" rel="alternate" />
  <updated>2026-03-16T17:43:08Z</updated>
  <id>https://d.moonfire.us/tags/encryption/</id>
  <author>
    <name>D. Moonfire</name>
  </author>
  <rights>Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International</rights>
  <entry>
    <title>Enabling SSL</title>
    <link rel="alternate" href="https://d.moonfire.us/blog/2014/06/07/enabling-ssl/" />
    <updated>2014-06-07T05:00:00Z</updated>
    <id>https://d.moonfire.us/blog/2014/06/07/enabling-ssl/</id>
    <category term="programming" scheme="https://d.moonfire.us/categories/" label="Programming" />
    <category term="encryption" scheme="https://d.moonfire.us/tags/" label="Encryption" />
    <category term="privacy" scheme="https://d.moonfire.us/tags/" label="Privacy" />
    <summary type="html">To help support Reset the Net, I enabled SSL on my personal blog.</summary>
    <content type="html">&lt;p&gt;A few days ago, I saw an interesting post over on the &lt;a href="http://piwik.org/blog/2014/06/resetthenet/"&gt;Piwik's blog&lt;/a&gt;. It was for &lt;a href="https://www.resetthenet.org/"&gt;Reset the Net&lt;/a&gt;, a general effort to try and get back some of the privacy of the Internet. In specific, a call for website operators to use SSL and encryption technologies.&lt;/p&gt;
&lt;p&gt;Now, I'm a proponent of privacy. I want everyone to use PGP or GnuPG to encrypt their emails, but only one person has done that in ten years. Everyone else goes &amp;ldquo;who cares?&amp;rdquo; and just moves on (or stops talking to me). And using PGP is rather difficult with webmail, which means I have to jump through a lot of hoops to even send out PGP email (and there are no good open source webmail clients that support PGP).&lt;/p&gt;
&lt;p&gt;The Reset the Net idea is a pretty good one, but it also fits in line with my philosophy. I don't have anything to hide, but I will fight for the rights of others to do so because someday, it may be important for all of us. Since I can't get people to send me encrypted emails, I didn't think I couldn't do much more besides talk about it.&lt;/p&gt;
&lt;p&gt;However, when I saw &lt;em&gt;Reset&lt;/em&gt;, I remembered that &lt;a href="http://www.dreamhost.com/r.cgi?80519"&gt;DreamHost&lt;/a&gt; mentioned something about &lt;a href="http://en.wikipedia.org/wiki/Server_Name_Indication"&gt;SNI&lt;/a&gt; and SSL. SNI doesn't work with old browsers, but given the support, I think I'm okay with that. It is &amp;ldquo;good enough&amp;rdquo; with most evergreen browsers out there. The biggest problem came down to getting an SSL certificate. At work, each one is hundreds of dollars and a major process. But then I remember that there is (relatively) small company that was providing free personal SSL certificates. It took me only a little bit of looking (on DreamHost's) site to find it: &lt;a href="https://www.startssl.com/"&gt;StartSSL&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It didn't take long for me to figure out something I could do. So, this morning, I created myself a brand new SSL certificate and installed it on my blog. And then helpfully created an &lt;code&gt;.htaccess&lt;/code&gt; to move viewers over to the SSL version.&lt;/p&gt;
&lt;p&gt;There is absolutely nothing on this website that is Not Safe For Work nor is there anything that is morally questionable with my content. I just think that SSL should be used for most traffic (much like Facebook, Google, and other places have enabled it) just like I would prefer to see all emails encrypted.&lt;/p&gt;
&lt;p&gt;It isn't much, but it is a step in what I think is the right direction.&lt;/p&gt;
&lt;p&gt;I'll move the rest of my domains over to SSL so when June 5th comes around again next year, I can safely say that I have done my bit to help.&lt;/p&gt;
</content>
  </entry>
</feed>
