<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Insufficient.Coffee - crlite</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/crlite/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://insufficient.coffee"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2020-12-01T00:00:00+00:00</updated>
    <id>https://insufficient.coffee/tag/crlite/atom.xml</id>
    <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>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>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>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>
</feed>