<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Insufficient.Coffee</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/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://insufficient.coffee"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-03-24T00:00:00+00:00</updated>
    <id>https://insufficient.coffee/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>The Open Source Cryptography Workshop is returning for 2026</title>
        <published>2025-11-06T00:00:00+00:00</published>
        <updated>2025-11-06T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2025/11/06/oscw-2026/"/>
        <id>https://insufficient.coffee/2025/11/06/oscw-2026/</id>
        
        <summary type="html">&lt;p&gt;After taking a year off from organizing OSCW 2025, I&#x27;m back for &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;opensourcecryptowork.shop&#x2F;2026&#x2F;&quot;&gt;next year&#x27;s event in Taipei&lt;&#x2F;a&gt;.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Attending Real World Crypto and the Open Source Cryptography Workshop 2024</title>
        <published>2024-03-14T00:00:00+00:00</published>
        <updated>2024-03-14T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2024/03/14/rwc-and-oscw-2024/"/>
        <id>https://insufficient.coffee/2024/03/14/rwc-and-oscw-2024/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;ll be attending the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;rwc.iacr.org&#x2F;2024&#x2F;&quot;&gt;Real World Crypto Symposium in Toronto&lt;&#x2F;a&gt; in two weeks time, and after that, I&#x27;m once again co-organizing the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;opensourcecryptowork.shop&#x2F;2024&#x2F;&quot;&gt;Open Source Cryptography Workshop&lt;&#x2F;a&gt;.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Make It Memory Safe: Adapting curl to use Rustls</title>
        <published>2023-03-30T00:00:00+00:00</published>
        <updated>2023-03-30T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2023/03/30/opensource-crypto-workshop-rustls-ffi/"/>
        <id>https://insufficient.coffee/2023/03/30/opensource-crypto-workshop-rustls-ffi/</id>
        
        <summary type="html">&lt;p&gt;As I mentioned in my post about attending &lt;a href=&quot;&#x2F;2023&#x2F;03&#x2F;21&#x2F;rwc-and-opensource-crypto-workshop-2023&#x2F;&quot;&gt;Real World Crypto 2023 and the Open Source Cryptography Workshop&lt;&#x2F;a&gt;, I&#x27;ve given a talk discussing &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;rustls&#x2F;rustls-ffi&#x2F;&quot;&gt;Rustls-FFI&lt;&#x2F;a&gt; and the work to allow &lt;code&gt;curl&lt;&#x2F;code&gt; and &lt;code&gt;libcurl&lt;&#x2F;code&gt; to use the Rust-based, memory-safe &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;rustls&#x2F;rustls&quot;&gt;Rustls TLS library&lt;&#x2F;a&gt; in a talk called &lt;em&gt;Make It Memory Safe: Adapting Curl to use Rustls&lt;&#x2F;em&gt;.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Nevermind about RWC and OSCW: COVID instead</title>
        <published>2023-03-25T00:00:00+00:00</published>
        <updated>2023-03-25T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2023/03/25/nevermind-about-rwc-and-oscw/"/>
        <id>https://insufficient.coffee/2023/03/25/nevermind-about-rwc-and-oscw/</id>
        
        <summary type="html">&lt;p&gt;At this point I&#x27;m supposed to be in Tokyo, attending the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;rwc.iacr.org&#x2F;2023&#x2F;&quot;&gt;Real World Crypto Symposium in Tokyo&lt;&#x2F;a&gt; next week, and after that, I&#x27;m co-organizing and &lt;a href=&quot;&#x2F;speaking-engagements&#x2F;&quot;&gt;speaking at&lt;&#x2F;a&gt; the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;opensourcecryptowork.shop&#x2F;2023&#x2F;&quot;&gt;Open Source Cryptography Workshop&lt;&#x2F;a&gt;. But I&#x27;ve gotten COVID-19 again, instead.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Attending Real World Crypto and the Open Source Cryptography Workshop 2023</title>
        <published>2023-03-21T00:00:00+00:00</published>
        <updated>2023-03-21T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2023/03/21/rwc-and-opensource-crypto-workshop-2023/"/>
        <id>https://insufficient.coffee/2023/03/21/rwc-and-opensource-crypto-workshop-2023/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;ll be attending the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;rwc.iacr.org&#x2F;2023&#x2F;&quot;&gt;Real World Crypto Symposium in Tokyo&lt;&#x2F;a&gt; next week, and after that, I&#x27;m co-organizing and &lt;a href=&quot;&#x2F;speaking-engagements&#x2F;&quot;&gt;speaking at&lt;&#x2F;a&gt; the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;opensourcecryptowork.shop&#x2F;2023&#x2F;&quot;&gt;Open Source Cryptography Workshop&lt;&#x2F;a&gt;.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Moving Human Blood Around Arizona</title>
        <published>2021-08-06T00:00:00+00:00</published>
        <updated>2021-08-06T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2021/08/06/moving-blood/"/>
        <id>https://insufficient.coffee/2021/08/06/moving-blood/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;d never thought about the logistics of moving donated blood around. The actual donation part is known to be a universally good thing to do, but I&#x27;d never searched out what happens next until I heard a fellow pilot talk about volunteering to move platelets around Arizona.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Design of the CRLite Infrastructure</title>
        <published>2020-12-01T00:00:00+00:00</published>
        <updated>2020-12-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/12/01/crlite-part-4-infrastructure-design/"/>
        <id>https://insufficient.coffee/2020/12/01/crlite-part-4-infrastructure-design/</id>
        
        <summary type="html">&lt;p&gt;Firefox is the only major browser that still evaluates every website it connects to whether the certificate used has been reported as revoked. Firefox users are notified of all connections involving untrustworthy certificates, regardless the popularity of the site. Inconveniently, checking certificate status sometimes slows down the connection to websites. Worse, the check reveals cleartext information about the website you’re visiting to network observers.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Auditing the CRLs in CRLite</title>
        <published>2020-11-27T00:00:00+00:00</published>
        <updated>2020-11-27T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/11/27/auditing-crls-of-crlite/"/>
        <id>https://insufficient.coffee/2020/11/27/auditing-crls-of-crlite/</id>
        
        <summary type="html">&lt;p&gt;Since Firefox Nightly is now using &lt;a href=&quot;&#x2F;tag&#x2F;crlite&quot;&gt;CRLite&lt;&#x2F;a&gt; to determine if enrolled websites&#x27; certificates are revoked, it&#x27;s useful to dig into the data to answer why a given certificate issuer gets enrolled or not.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Querying CRLite for WebPKI Revocations</title>
        <published>2020-11-26T00:00:00+00:00</published>
        <updated>2020-11-26T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/11/26/querying-crlite/"/>
        <id>https://insufficient.coffee/2020/11/26/querying-crlite/</id>
        
        <summary type="html">&lt;p&gt;Firefox Nightly is now using &lt;a href=&quot;&#x2F;tag&#x2F;crlite&quot;&gt;CRLite&lt;&#x2F;a&gt; to determine if websites&#x27; certificates are revoked — e.g., if the Certificate Authority published that web browsers shouldn&#x27;t trust that website certificate. Telemetry shows that querying the local CRLite dataset is much faster than making a network connection for &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Online_Certificate_Status_Protocol&quot;&gt;OCSP&lt;&#x2F;a&gt;, which makes intuitive sense. It also avoids sending the website&#x27;s certificate information in cleartext over the network to check the revocation status: solving one of the remaining cleartext browsing data leakages in Firefox.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Austin or Bust: A Post-Y&#x27;allhands Adventure</title>
        <published>2020-11-01T00:00:00+00:00</published>
        <updated>2020-11-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/11/01/austin-or-bust/"/>
        <id>https://insufficient.coffee/2020/11/01/austin-or-bust/</id>
        
        <summary type="html">&lt;p&gt;Due to a variety of factors, Mozilla changed venues for our 2017 winter all-hands meeting to Austin, Texas, and Austin being a city with relatively poor commercial airline connectivity, ticket prices were fairly high even for me to fly there from Phoenix.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Berlin By Air</title>
        <published>2020-10-05T00:00:00+00:00</published>
        <updated>2020-10-05T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/10/05/berlin-by-air/"/>
        <id>https://insufficient.coffee/2020/10/05/berlin-by-air/</id>
        
        <summary type="html">&lt;p&gt;I have had business dealings requiring me to visit Berlin regularly for the last 5 years, and in 2018 I finally made the trip outside of the city to &lt;a href=&quot;https:&#x2F;&#x2F;acukwik.com&#x2F;Airport-Info&#x2F;EDAY&quot;&gt;Strausberg Airport&lt;&#x2F;a&gt; to rent a Cessna 172SP Skyhawk.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Returning Home and Flying in Northwest Florida</title>
        <published>2020-09-30T00:00:00+00:00</published>
        <updated>2020-09-30T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/09/30/returning-home/"/>
        <id>https://insufficient.coffee/2020/09/30/returning-home/</id>
        
        <summary type="html">&lt;p&gt;While I lived in a lot of different places as a child, I came of age along the Florida panhandle, and for that reason it&#x27;ll always hold a special place in my heart.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Watching Hawaii Boil the Pacific Ocean</title>
        <published>2020-09-29T00:00:00+00:00</published>
        <updated>2020-09-29T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/09/29/boiling-the-ocean/"/>
        <id>https://insufficient.coffee/2020/09/29/boiling-the-ocean/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;ve had a lot more opportunity to travel since I joined &lt;a href=&quot;&#x2F;tag&#x2F;mozilla&quot;&gt;Mozilla&lt;&#x2F;a&gt;, and it eventually occurred to me: I could rent aircraft in some of these places I was visiting, and see those places in a different way.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Blog upgrades and a long-awaited new domain, insufficient.coffee</title>
        <published>2020-06-25T00:00:00+00:00</published>
        <updated>2020-06-25T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/06/25/blog_upgrades/"/>
        <id>https://insufficient.coffee/2020/06/25/blog_upgrades/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;ve been running this blog on an LTS version of Ubuntu that has recently halted Long Term Support,
so while migrating data I&#x27;m also reworking parts of this blog, including a long-anticipated move
from &lt;a href=&quot;https:&#x2F;&#x2F;insufficient.coffee&#x2F;2020&#x2F;06&#x2F;25&#x2F;blog_upgrades&#x2F;tacticalsecret.com&quot;&gt;tacticalsecret.com&lt;&#x2F;a&gt; (what a ... term) to the timeless
domain &lt;a href=&quot;https:&#x2F;&#x2F;insufficient.coffee&#x2F;2020&#x2F;06&#x2F;25&#x2F;blog_upgrades&#x2F;insufficient.coffee&quot;&gt;insufficient.coffee&lt;&#x2F;a&gt;.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>CRLite: Speeding Up Secure Browsing</title>
        <published>2020-01-21T00:00:00+00:00</published>
        <updated>2020-01-21T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/01/21/crlite-part-3-speeding-up-secure-browsing/"/>
        <id>https://insufficient.coffee/2020/01/21/crlite-part-3-speeding-up-secure-browsing/</id>
        
        <summary type="html">&lt;p&gt;CRLite pushes bulk certificate revocation information to Firefox users, reducing the need to actively query such information one by one. Additionally this new technology eliminates the privacy leak that individual queries can bring, and does so for the whole Web, not just special parts of it.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Introducing CRLite: All of the Web PKI’s revocations, compressed</title>
        <published>2020-01-09T00:00:00+00:00</published>
        <updated>2020-01-09T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/01/09/crlite-part-1-all-web-pki-revocations-compressed/"/>
        <id>https://insufficient.coffee/2020/01/09/crlite-part-1-all-web-pki-revocations-compressed/</id>
        
        <summary type="html">&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;obj.umiacs.umd.edu&#x2F;papers_for_stories&#x2F;crlite_oakland17.pdf&quot;&gt;CRLite&lt;&#x2F;a&gt; is a technology proposed by a group of researchers at the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;www.ieee-security.org&#x2F;TC&#x2F;SP2017&#x2F;&quot;&gt;IEEE Symposium on Security and Privacy 2017&lt;&#x2F;a&gt; that compresses revocation information so effectively that 300 megabytes of revocation data can become 1 megabyte.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>The End-to-End Design of CRLite</title>
        <published>2020-01-09T00:00:00+00:00</published>
        <updated>2020-01-09T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2020/01/09/crlite-part-2-end-to-end-design/"/>
        <id>https://insufficient.coffee/2020/01/09/crlite-part-2-end-to-end-design/</id>
        
        <summary type="html">&lt;p&gt;CRLite is a technology to efficiently compress revocation information for the whole Web PKI into a format easily delivered to Web users. It addresses the performance and privacy pitfalls of the Online Certificate Status Protocol (OCSP) while avoiding a need for some administrative decisions on the relative value of one revocation versus another.&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Web Authentication in Firefox for Android</title>
        <published>2019-08-05T00:00:00+00:00</published>
        <updated>2019-08-05T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2019/08/05/web-authentication-in-firefox-for-android/"/>
        <id>https://insufficient.coffee/2019/08/05/web-authentication-in-firefox-for-android/</id>
        
        <summary type="html">&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;www.mozilla.org&#x2F;en-US&#x2F;firefox&#x2F;android&#x2F;all&#x2F;&quot;&gt;Firefox for Android (Fennec)&lt;&#x2F;a&gt; now supports the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;API&#x2F;Web_Authentication_API&quot;&gt;Web Authentication API&lt;&#x2F;a&gt; as of &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;www.mozilla.org&#x2F;en-US&#x2F;firefox&#x2F;android&#x2F;68.0&#x2F;releasenotes&#x2F;&quot;&gt;version 68&lt;&#x2F;a&gt;.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Making HTTPS Revocations Work: CRLite (Lightning Talk)</title>
        <published>2018-12-04T00:00:00+00:00</published>
        <updated>2018-12-04T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2018/12/04/making-https-revocations-work-crlite/"/>
        <id>https://insufficient.coffee/2018/12/04/making-https-revocations-work-crlite/</id>
        
        <summary type="html">&lt;p&gt;I gave a lightning talk at our Mozilla All-Hands meeting about &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;obj.umiacs.umd.edu&#x2F;papers_for_stories&#x2F;crlite_oakland17.pdf&quot;&gt;CRLite&lt;&#x2F;a&gt;, a new technology for delivering revocations for the Web PKI to all clients in a very compressed form.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Trying Out Web Authentication (WebAuthn)</title>
        <published>2018-01-11T00:00:00+00:00</published>
        <updated>2018-01-11T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/trying-out-web-authentication-webauthn/"/>
        <id>https://insufficient.coffee/trying-out-web-authentication-webauthn/</id>
        
        <summary type="html">&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;w3c.github.io&#x2F;webauthn&#x2F;&quot;&gt;Web Authentication&lt;&#x2F;a&gt; is now &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;twitter.com&#x2F;FirefoxNightly&#x2F;status&#x2F;951428981907165186&quot;&gt;enabled in Firefox Nightly&lt;&#x2F;a&gt;, with &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!msg&#x2F;mozilla.dev.platform&#x2F;tsevyqfBHLE&#x2F;lccldWNNBwAJ&quot;&gt;intent to ship in version 60&lt;&#x2F;a&gt;.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Countering Phishing with Cryptography - WebAuthn (Lightning Talk)</title>
        <published>2017-12-04T00:00:00+00:00</published>
        <updated>2017-12-04T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2017/12/04/countering-phishing-with-cryptography/"/>
        <id>https://insufficient.coffee/2017/12/04/countering-phishing-with-cryptography/</id>
        
        <summary type="html">&lt;p&gt;At Mozilla&#x27;s Austin All-Hands I gave a lightning talk about &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;API&#x2F;Web_Authentication_API&quot;&gt;Web Authentication&lt;&#x2F;a&gt;, which is our best technical solution to the scourge of phishing today.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>The State of CRLs Today</title>
        <published>2017-08-18T00:00:00+00:00</published>
        <updated>2017-08-18T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/the-state-of-crls/"/>
        <id>https://insufficient.coffee/the-state-of-crls/</id>
        
        <summary type="html">&lt;p&gt;Certificate Revocation Lists (CRLs) are a way for Certificate Authorities to announce to their relying parties (e.g., users validating the certificates) that a Certificate they issued should no longer be trusted. E.g., was revoked.&amp;hellip;
&lt;&#x2F;p&gt;
</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>The end of SHA-1 on the Public Web</title>
        <published>2017-02-23T00:00:00+00:00</published>
        <updated>2017-02-23T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/2017/02/23/the-end-of-sha-1-on-the-public-web/"/>
        <id>https://insufficient.coffee/2017/02/23/the-end-of-sha-1-on-the-public-web/</id>
        
        <summary type="html">&lt;p&gt;Our deprecation plan for the SHA-1 algorithm in the public Web, &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;blog.mozilla.org&#x2F;security&#x2F;2015&#x2F;10&#x2F;20&#x2F;continuing-to-phase-out-sha-1-certificates&#x2F;&quot;&gt;first announced in 2015&lt;&#x2F;a&gt;, is drawing to a close. Today a team of researchers from CWI Amsterdam and Google revealed the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;security.googleblog.com&#x2F;2017&#x2F;02&#x2F;announcing-first-sha1-collision.html&quot;&gt;first practical collision for SHA-1&lt;&#x2F;a&gt;, affirming the insecurity of the algorithm and reinforcing our judgment that it must be retired from security use on the Web.</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>A Big Tent in America</title>
        <published>2016-11-10T00:00:00+00:00</published>
        <updated>2016-11-10T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/a-big-tent-in-america/"/>
        <id>https://insufficient.coffee/a-big-tent-in-america/</id>
        
        <summary type="html">&lt;p&gt;The electoral college has legitimized an agenda that seeks to tell many of my friends and colleagues that they are not welcome in America. That they are only to be tolerated in the shadows. That denigrating them is acceptable national discourse, and will be rewarded with prestige.&amp;hellip;
&lt;&#x2F;p&gt;
</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>Long Instrument Cross-Country Training Flight</title>
        <published>2016-09-08T00:00:00+00:00</published>
        <updated>2016-09-08T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/long-instrument-cross-country-training-flight/"/>
        <id>https://insufficient.coffee/long-instrument-cross-country-training-flight/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;m training to be able to fly in clouds and other poor visibility situations. Part of the requirements for this &quot;Instrument Rating&quot; is to fly cross-country, on instrument rules, and do instrument landings at three airports, a task I undertook last Friday&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Utility of an Instrument Rating</title>
        <published>2016-08-11T00:00:00+00:00</published>
        <updated>2016-08-11T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/utility-of-an-instrument-rating/"/>
        <id>https://insufficient.coffee/utility-of-an-instrument-rating/</id>
        
        <summary type="html">&lt;p&gt;I am training right now for my &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;Instrument_rating&quot;&gt;instrument rating add-on&lt;&#x2F;a&gt; to my private pilot certificate. For years I said that there was little point to me having this rating, because in Arizona, when there &lt;em&gt;is&lt;&#x2F;em&gt; weather, you don&#x27;t want to fly in it.</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>Content Security Policy Enabled</title>
        <published>2016-01-19T00:00:00+00:00</published>
        <updated>2016-01-19T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/content-security-policy-enabled/"/>
        <id>https://insufficient.coffee/content-security-policy-enabled/</id>
        
        <summary type="html">&lt;p&gt;I spent some time over the last week working up a safe &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;Security&#x2F;CSP&quot;&gt;Content Security Policy&lt;&#x2F;a&gt; for this website</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>
    <entry xml:lang="en">
        <title>Updated JSONResume</title>
        <published>2014-11-20T00:00:00+00:00</published>
        <updated>2014-11-20T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/updated-jsonresume/"/>
        <id>https://insufficient.coffee/updated-jsonresume/</id>
        
        <summary type="html">&lt;p&gt;I&#x27;ve posted a new version of my &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;www.npmjs.org&#x2F;package&#x2F;jsonresume-theme-bootstrap-icons&quot;&gt;Bootstrap Icons&lt;&#x2F;a&gt; theme for &lt;a rel=&quot;external&quot; href=&quot;http:&#x2F;&#x2F;jsonresume.org&quot;&gt;JsonResume&lt;&#x2F;a&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Net Neutrality</title>
        <published>2014-11-18T00:00:00+00:00</published>
        <updated>2014-11-18T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/net-neutrality/"/>
        <id>https://insufficient.coffee/net-neutrality/</id>
        
        <summary type="html">&lt;p&gt;Last night I received this political cartoon in my email:&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Service Assisted Communication and Simplifying a PKI</title>
        <published>2014-09-09T00:00:00+00:00</published>
        <updated>2014-09-09T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/simplifying-pki-iot/"/>
        <id>https://insufficient.coffee/simplifying-pki-iot/</id>
        
        <summary type="html">&lt;p&gt;Because many of the devices in the IoT are headless and have limited ability to interact with their owners, there needs to be a way to authenticate them without passwords, and without the shortcomings of the existing &lt;a rel=&quot;external&quot; href=&quot;http:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Bluetooth#Pairing_mechanisms&quot;&gt;0000 and 1234 problems&lt;&#x2F;a&gt; in the Bluetooth world.</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>JSONResume</title>
        <published>2014-08-12T00:00:00+00:00</published>
        <updated>2014-08-12T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/jsonresume/"/>
        <id>https://insufficient.coffee/jsonresume/</id>
        
        <summary type="html">&lt;p&gt;There&#x27;s a quirky little project on the Internet proving once again that semi-structured data is just plain fun: &lt;a rel=&quot;external&quot; href=&quot;http:&#x2F;&#x2F;jsonresume.org&#x2F;&quot;&gt;JSONResume.org&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Garden Imp</title>
        <published>2014-08-06T00:00:00+00:00</published>
        <updated>2014-08-06T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/garden-imp/"/>
        <id>https://insufficient.coffee/garden-imp/</id>
        
        <summary type="html">&lt;p&gt;Using an &lt;a rel=&quot;external&quot; href=&quot;http:&#x2F;&#x2F;electricimp.com&#x2F;&quot;&gt;Electric Imp&lt;&#x2F;a&gt; and two &lt;a rel=&quot;external&quot; href=&quot;http:&#x2F;&#x2F;vegetronix.com&#x2F;Products&#x2F;VH400&#x2F;&quot;&gt;Vegetronix VH400 soil moisture sensors&lt;&#x2F;a&gt;, I am now able to monitor the &lt;a rel=&quot;external&quot; href=&quot;http:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Water_content&quot;&gt;water content&lt;&#x2F;a&gt; of two locations in my garden.&lt;&#x2F;p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Different PAN Parts: Auth-Only, Confidential and No Consequence</title>
        <published>2014-08-06T00:00:00+00:00</published>
        <updated>2014-08-06T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/pan-parts-iot/"/>
        <id>https://insufficient.coffee/pan-parts-iot/</id>
        
        <summary type="html">&lt;p&gt;Where the Internet of Things meets locations in the physical world, I envision scores of devices networking together to make life more efficient&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Public Authentication</title>
        <published>2014-07-30T00:00:00+00:00</published>
        <updated>2014-07-30T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/public-authentication/"/>
        <id>https://insufficient.coffee/public-authentication/</id>
        
        <summary type="html">&lt;p&gt;The public authentication problem is one we have all learned to solve with intuition: &lt;em&gt;How do I decide to trust a new person?&lt;&#x2F;em&gt;&amp;hellip;
&lt;&#x2F;p&gt;
</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Prevalence of Well Known Peers in the Internet of Things</title>
        <published>2014-07-04T00:00:00+00:00</published>
        <updated>2014-07-04T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://insufficient.coffee/well-known-peers-iot/"/>
        <id>https://insufficient.coffee/well-known-peers-iot/</id>
        
        <summary type="html">&lt;p&gt;The Internet of Things is imagined to be a interconnection of sensors and physical devices of all kinds into the world’s information systems: a collection of machine-to-machine communication devices used to gather and distribute information about the world, contrasted with the human-machine interactions making up the bulk of today’s Internet. The machine-to-machine model places new restrictions on the common practices for security, as the standard practice of user authentication becomes troublesome without the regular involvement of a user.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>