<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Insufficient.Coffee - letsencrypt</title>
    <subtitle>On a mission to solve communications security issues for the whole Internet. That, and drink coffee.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://insufficient.coffee/tag/letsencrypt/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://insufficient.coffee"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2025-12-03T00:00:00+00:00</updated>
    <id>https://insufficient.coffee/tag/letsencrypt/atom.xml</id>
    <entry xml:lang="en">
        <title>Reflecting on 10 years of Let&#x27;s Encrypt</title>
        <published>2025-12-03T00:00:00+00:00</published>
        <updated>2025-12-03T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2025/12/03/reflecting-on-lets-encrypt/"/>
        <id>https://insufficient.coffee/2025/12/03/reflecting-on-lets-encrypt/</id>
        
        <summary type="html">&lt;p&gt;My friend Christophe Brocas has just &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;blog.brocas.org&#x2F;2025&#x2F;12&#x2F;01&#x2F;ACME-a-brief-history-of-one-of-the-protocols-which-has-changed-the-Internet-Security&#x2F;&quot;&gt;published a retrospective on the ten years since we unveiled the ACME protocol to the world&lt;&#x2F;a&gt;. He interviewed me and some colleagues for the piece, and I recommend it!</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Cutting over Let&#x27;s Encrypt&#x27;s Statistics to Map&#x2F;Reduce</title>
        <published>2017-07-10T00:00:00+00:00</published>
        <updated>2017-07-10T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/cutting-over-lets-encrypts-statistics-to-map-reduce/"/>
        <id>https://insufficient.coffee/cutting-over-lets-encrypts-statistics-to-map-reduce/</id>
        
        <summary type="html">&lt;p&gt;We&#x27;re &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;tacticalsecret.com&#x2F;analyzing-letsencrypt-stats-via-map-reduce&#x2F;&quot;&gt;changing the methodology&lt;&#x2F;a&gt; used to calculate the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;letsencrypt.org&#x2F;stats&#x2F;&quot;&gt;Let&#x27;s Encrypt Statistics page&lt;&#x2F;a&gt;, primarily to better cope with the growth of Let&#x27;s Encrypt. Over the past several months it&#x27;s become clear that the existing methodology is less accurate than we had expected, over-counting the number of websites using Let&#x27;s Encrypt, and the number of active certificates. The new methodology is more easily spot-checked, and thus, we believe, is more accurate.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Analyzing Let&#x27;s Encrypt statistics via Map&#x2F;Reduce</title>
        <published>2017-05-16T00:00:00+00:00</published>
        <updated>2017-05-16T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/analyzing-letsencrypt-stats-via-map-reduce/"/>
        <id>https://insufficient.coffee/analyzing-letsencrypt-stats-via-map-reduce/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;ve been supplying the statistics for Let&#x27;s Encrypt since they&#x27;ve launched. In Q4 of 2016 their volume of certificates exceeded the ability of my database server to cope, and I moved it to an Amazon RDS instance.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Demoing Let&#x27;s Encrypt at the Phoenix DevOps Meetup in February</title>
        <published>2016-12-19T00:00:00+00:00</published>
        <updated>2016-12-19T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/demoing-lets-encrypt-at-the-phoenix-devops-meetup-in-february/"/>
        <id>https://insufficient.coffee/demoing-lets-encrypt-at-the-phoenix-devops-meetup-in-february/</id>
        
        <summary type="html">&lt;p&gt;The Phoenix DevOps Meetup has asked me to do a &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;www.meetup.com&#x2F;Phoenix-DevOps-Meetup&#x2F;events&#x2F;236338847&#x2F;&quot;&gt;walk-through of how to encrypt  a website using Let&#x27;s Encrypt for their February meetup&lt;&#x2F;a&gt;. I don&#x27;t believe this talk will be recorded, but for any locals who want to discuss PKI, I&#x27;ll be available after.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Let&#x27;s Encrypt&#x27;s Growth to 10 Million Active Unique FQDNs</title>
        <published>2016-09-30T00:00:00+00:00</published>
        <updated>2016-09-30T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/lets-encrypts-growth-to-10m-fqdns/"/>
        <id>https://insufficient.coffee/lets-encrypts-growth-to-10m-fqdns/</id>
        
        <summary type="html">&lt;p&gt;Yesterday Let&#x27;s Encrypt reached a new milestone: the unique set of all fully-qualified domain names in the currently-unexpired certificates issued by Let&#x27;s Encrypt is now &lt;strong&gt;10,022,446&lt;&#x2F;strong&gt;.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>The Road to Encrypting All The Things: RMLL 2016 (Paris)</title>
        <published>2016-07-05T00:00:00+00:00</published>
        <updated>2016-07-05T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/rmll2016/"/>
        <id>https://insufficient.coffee/rmll2016/</id>
        
        <summary type="html">&lt;p&gt;Today at the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;sec2016.rmll.info&#x2F;program&#x2F;&quot;&gt;RMLL conference&#x27;s security track&lt;&#x2F;a&gt; I&#x27;m talking about some of the challenges, decisions, and trade-offs that occurred while launching Let&#x27;s Encrypt, in a talk I&#x27;ve called  &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;sec2016.rmll.info&#x2F;program&#x2F;#letsencrypt&quot;&gt;Let’s Encrypt: The Road To Encrypting All The Things&lt;&#x2F;a&gt;.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>124 Days of Let&#x27;s Encrypt</title>
        <published>2016-04-05T00:00:00+00:00</published>
        <updated>2016-04-05T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/124-days-of-lets-encrypt/"/>
        <id>https://insufficient.coffee/124-days-of-lets-encrypt/</id>
        
        <summary type="html">&lt;p&gt;This is a quick status update from the &lt;a href=&quot;&#x2F;early-impacts-of-letsencrypt&#x2F;&quot;&gt;Early Impacts of Let&#x27;s Encrypt&lt;&#x2F;a&gt; post.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Early Impacts of Let&#x27;s Encrypt</title>
        <published>2016-02-19T00:00:00+00:00</published>
        <updated>2016-02-19T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/early-impacts-of-letsencrypt/"/>
        <id>https://insufficient.coffee/early-impacts-of-letsencrypt/</id>
        
        <summary type="html">&lt;p&gt;During the months I worked in Let&#x27;s Encrypt&#x27;s operations team I got fairly used to being the go-to man for any question that a database query could solve.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Issuance Rate for Let&#x27;s Encrypt</title>
        <published>2016-01-21T00:00:00+00:00</published>
        <updated>2016-01-21T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/issuance-rate-for-lets-encrypt/"/>
        <id>https://insufficient.coffee/issuance-rate-for-lets-encrypt/</id>
        
        <summary type="html">&lt;p&gt;Gathering data from &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;jcjones&#x2F;letsencrypt_statistics&quot;&gt;Certificate Transparency logs&lt;&#x2F;a&gt;, here&#x27;s a snapshot in time of Let&#x27;s Encrypt&#x27;s certificate issuance rate per minute from 15-21 January 2016</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Renewing Let&#x27;s Encrypt Certs (Nginx)</title>
        <published>2016-01-15T00:00:00+00:00</published>
        <updated>2016-01-15T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/renewing-lets-encrypt-certs-nginx/"/>
        <id>https://insufficient.coffee/renewing-lets-encrypt-certs-nginx/</id>
        
        <summary type="html">&lt;p&gt;All the first &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;crt.sh&#x2F;?id=10172479&quot;&gt;Let&#x27;s Encrypt certs for my websites&lt;&#x2F;a&gt; from the LE private beta began expiring last week, so it was time to work through the renewal tooling</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Let&#x27;s Encrypt: Publicly Trusted</title>
        <published>2015-10-20T00:00:00+00:00</published>
        <updated>2015-10-20T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/lets-encrypt-publicly-trusted/"/>
        <id>https://insufficient.coffee/lets-encrypt-publicly-trusted/</id>
        
        <summary type="html">&lt;p&gt;A bigger blog post will have to wait, but just as a brief note:&lt;&#x2F;p&gt;
&lt;p&gt;Let&#x27;s Encrypt is &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;letsencrypt.org&#x2F;2015&#x2F;10&#x2F;19&#x2F;lets-encrypt-is-trusted.html&quot;&gt;now publicly trusted&lt;&#x2F;a&gt;. In fact, this blog is using a certificate from Let&#x27;s Encrypt. And so is &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;usr.bin.coffee&#x2F;&quot;&gt;usr.bin.coffee&lt;&#x2F;a&gt;, of course.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Beta Testing Let&#x27;s Encrypt</title>
        <published>2015-10-08T00:00:00+00:00</published>
        <updated>2015-10-08T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/beta-testing-lets-encrypt/"/>
        <id>https://insufficient.coffee/beta-testing-lets-encrypt/</id>
        
        <summary type="html">&lt;p&gt;One of the advantages to being part of the Let&#x27;s Encrypt team is early access to the closed beta. As such, I&#x27;ve been able to issue a handful of certificates from the service. For example: &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;usr.bin.coffee&#x2F;&quot;&gt;usr.bin.coffee&lt;&#x2F;a&gt;. There&#x27;s a lot of other upsides as well, such as working with incredible people to make something super-high visibility for the public good.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>GatorLUG Presentation on Let&#x27;s Encrypt</title>
        <published>2015-04-10T00:00:00+00:00</published>
        <updated>2015-04-10T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/gatorlug-letsencrypt/"/>
        <id>https://insufficient.coffee/gatorlug-letsencrypt/</id>
        
        <summary type="html">&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;http:&#x2F;&#x2F;www.gatorlug.org&#x2F;&quot;&gt;GatorLUG&lt;&#x2F;a&gt; has invited me to talk about &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;letsencrypt.org&#x2F;&quot;&gt;Let&#x27;s Encrypt&lt;&#x2F;a&gt; at their April 2015 meeting. I&#x27;m honored to be playing a role in the architecture and implementation of Let&#x27;s Encrypt; &lt;a href=&quot;&#x2F;content&#x2F;2015&#x2F;Apr&#x2F;Gator%20LUG%2020150415%20Lets%20Encrypt.pdf&quot;&gt;here are the slides I&#x27;ll be presenting&lt;&#x2F;a&gt;.</summary>
        
    </entry>
</feed>