<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: ssl</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/ssl.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2018-07-06T23:02:43+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting James Donohue</title><link href="https://simonwillison.net/2018/Jul/6/james-donohue/#atom-tag" rel="alternate"/><published>2018-07-06T23:02:43+00:00</published><updated>2018-07-06T23:02:43+00:00</updated><id>https://simonwillison.net/2018/Jul/6/james-donohue/#atom-tag</id><summary type="html">
    &lt;blockquote cite="https://medium.com/bbc-design-engineering/bbc-news-on-https-182b45ef60c"&gt;&lt;p&gt;Over the last twenty years, publishing systems for content on [BBC] News pages have come and gone, having been replaced or made obsolete. Although newer content is published through dynamic web applications that can be readily modified, what lies beneath this sometimes resembles layers of sedimentary rock.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://medium.com/bbc-design-engineering/bbc-news-on-https-182b45ef60c"&gt;James Donohue&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/bbc"&gt;bbc&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/bbcnews"&gt;bbcnews&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;



</summary><category term="bbc"/><category term="bbcnews"/><category term="ssl"/></entry><entry><title>Protecting Against HSTS Abuse</title><link href="https://simonwillison.net/2018/Mar/19/hsts-abuse/#atom-tag" rel="alternate"/><published>2018-03-19T22:21:57+00:00</published><updated>2018-03-19T22:21:57+00:00</updated><id>https://simonwillison.net/2018/Mar/19/hsts-abuse/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://webkit.org/blog/8146/protecting-against-hsts-abuse/"&gt;Protecting Against HSTS Abuse&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Any web feature that can be used to persist information will eventually be used to build super-cookies. In this case it’s HSTS—a web feature that allows sites to tell browsers “in the future always load this domain over HTTPS even if the request specified HTTP”. The WebKit team caught this being exploited in the wild, by encoding a user identifier in binary across 32 separate sub domains. They have a couple of mitigations in place now—I expect other browser vendors will follow suit.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://twitter.com/troyhunt/status/975816855838384128?s=21"&gt;@troyhunt&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/privacy"&gt;privacy&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/webkit"&gt;webkit&lt;/a&gt;&lt;/p&gt;



</summary><category term="privacy"/><category term="security"/><category term="ssl"/><category term="webkit"/></entry><entry><title>SSL Issuer Popularity</title><link href="https://simonwillison.net/2017/Nov/21/ssl-issuer-popularity/#atom-tag" rel="alternate"/><published>2017-11-21T14:44:56+00:00</published><updated>2017-11-21T14:44:56+00:00</updated><id>https://simonwillison.net/2017/Nov/21/ssl-issuer-popularity/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://nettrack.info/ssl_certificate_issuers.html"&gt;SSL Issuer Popularity&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The impressive growth of Let’s Encrypt in one graph: from 4.87% of TLS-enabled domains in May 2016 to 36.68% in November 2017.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="ssl"/></entry><entry><title>Side-Channel Leaks in Web Applications</title><link href="https://simonwillison.net/2010/Mar/23/sidechannel/#atom-tag" rel="alternate"/><published>2010-03-23T16:24:02+00:00</published><updated>2010-03-23T16:24:02+00:00</updated><id>https://simonwillison.net/2010/Mar/23/sidechannel/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.freedom-to-tinker.com/blog/felten/side-channel-leaks-web-applications"&gt;Side-Channel Leaks in Web Applications&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Interesting new security research. SSL web connections encrypt the content but an attacker can still see the size of the HTTP requests going back and forward—which can be enough to extract significant pieces of information, especially in applications that make a lot of Ajax requests.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ajax"&gt;ajax&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/http"&gt;http&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sidechannel"&gt;sidechannel&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;



</summary><category term="ajax"/><category term="http"/><category term="security"/><category term="sidechannel"/><category term="ssl"/></entry><entry><title>Researchers Show How to Forge Site Certificates</title><link href="https://simonwillison.net/2008/Dec/30/fake/#atom-tag" rel="alternate"/><published>2008-12-30T15:27:33+00:00</published><updated>2008-12-30T15:27:33+00:00</updated><id>https://simonwillison.net/2008/Dec/30/fake/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.freedom-to-tinker.com/blog/felten/researchers-show-how-forge-site-certificates"&gt;Researchers Show How to Forge Site Certificates&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Use an MD5 collision to create two certificates with the same hash, one for a domain you own and another for amazon.com. Get Equifax CA to sign your domain’s certificate using the outdated “MD5 with RSA” signing method. Copy that signature on to your home-made amazon.com certificate to create a fake certificate for Amazon that will be accepted by any browser.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/collisions"&gt;collisions&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ed-felten"&gt;ed-felten&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/equifaxca"&gt;equifaxca&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hashes"&gt;hashes&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/md5"&gt;md5&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;



</summary><category term="collisions"/><category term="ed-felten"/><category term="equifaxca"/><category term="hashes"/><category term="md5"/><category term="security"/><category term="ssl"/></entry><entry><title>the tls report</title><link href="https://simonwillison.net/2008/Jun/10/tls/#atom-tag" rel="alternate"/><published>2008-06-10T23:49:34+00:00</published><updated>2008-06-10T23:49:34+00:00</updated><id>https://simonwillison.net/2008/Jun/10/tls/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://tlsreport.layer8.net/"&gt;the tls report&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Clever service that analyses a web server’s SSL implementation and grades it based on things like the protocols, certificates, ciphers and key lengths it supports. Includes public reports on the top and bottom 20 sites.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://radar.oreilly.com/archives/2008/06/tlsreport-grade-report-website-security.html"&gt;O&amp;#x27;Reilly Radar&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tls"&gt;tls&lt;/a&gt;&lt;/p&gt;



</summary><category term="security"/><category term="ssl"/><category term="tls"/></entry><entry><title>MyOpenID relaunches</title><link href="https://simonwillison.net/2007/Apr/17/janrain/#atom-tag" rel="alternate"/><published>2007-04-17T15:40:40+00:00</published><updated>2007-04-17T15:40:40+00:00</updated><id>https://simonwillison.net/2007/Apr/17/janrain/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://janrain.com/blog/2007/04/17/myopenid-launches-secure-authentication-helps-prevent-phishing/"&gt;MyOpenID relaunches&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Now with a handsome redesign and support for SSL client certificates as a secure alternative to passwords.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/janrain"&gt;janrain&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/myopenid"&gt;myopenid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;



</summary><category term="janrain"/><category term="myopenid"/><category term="openid"/><category term="ssl"/></entry><entry><title>prooveme.com</title><link href="https://simonwillison.net/2007/Feb/22/prooveme/#atom-tag" rel="alternate"/><published>2007-02-22T12:01:58+00:00</published><updated>2007-02-22T12:01:58+00:00</updated><id>https://simonwillison.net/2007/Feb/22/prooveme/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://prooveme.com/"&gt;prooveme.com&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
An OpenID provider that uses SSL client certificates (which you install in your browser) for authentication.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/certificates"&gt;certificates&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/prooveme"&gt;prooveme&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;



</summary><category term="certificates"/><category term="openid"/><category term="prooveme"/><category term="ssl"/></entry><entry><title>Windows SSL support in Python</title><link href="https://simonwillison.net/2002/Jul/24/windowsSslSupportInPython/#atom-tag" rel="alternate"/><published>2002-07-24T13:06:01+00:00</published><updated>2002-07-24T13:06:01+00:00</updated><id>https://simonwillison.net/2002/Jul/24/windowsSslSupportInPython/#atom-tag</id><summary type="html">
    &lt;p&gt;Adding &lt;acronym title="Secure Socket Layer"&gt;SSL&lt;/acronym&gt; support to Python on Windows is as easy as dropping a couple of &lt;acronym title="Dynamic Link Libraries"&gt;DLLs&lt;/acronym&gt; and a &lt;code&gt;.pyd&lt;/code&gt; file in to your Python DLLs directory. Grab the zip file from &lt;a href="http://www.cs.fhm.edu/~ifw00065/pyssl/" title=" Python - SSL"&gt;this page&lt;/a&gt; and off you go. I haven't tried it out yet but it appears to work - the &lt;a href="http://www.python.org/doc/lib/module-socket.html#l2h-1866"&gt;socket.ssl&lt;/a&gt; function miraculously appeared when I installed the new files. Why is this useful? Because it opens the way for secure &lt;acronym title="exTensible Markup Language - Remote Procedure Calling"&gt;XML-RPC&lt;/acronym&gt; calls from Python applications...&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ssl"&gt;ssl&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="python"/><category term="ssl"/></entry></feed>