Hi Holger, On Tue, Dec 27, 2016 at 11:12:50PM +0100, Holger Just wrote: > Hi Willy, > > Recently, you updated the SSL certificate of haproxy.org, > git.haproxy.org, ... to a new certificate from StartSSL.
Yep and I was glad to be done with this painful stuff for 3 years... > Unfortunately, recently, there was an incident of several misissued > certificates by this CA as well as shady business decisions involving > WoSign which resulted in Chrome [1] and Firefox [2] no longer trusting > the CA's root certificates with their next respective releases. Apple > has revoked trust to certificates issued after December 1 [3] which just > barely doesn't affect the current cert. I have found no statement by > Microsoft. > > With the next release of Firefox and Chrome, users using the https > versions of the websites will thus receive a strongly worded error > similar to other TLS errors involving invalid certificates. Hmmm cool. The usual loop repeats itself... Google has the power to force every site to implement SSL, CAs mess up, browsers have the power to judge who must be disqualified, and in the end it's users who are annoyed. I'm impatient to see this long-obsolete single-chain trust model collapse. > I'd thus recommend to update the certificate again and use a more > trusted CA. With Let's Encrypt being widely supported, well automateable > and also free, I'd recommend this one. Thanks. Last time I checked it was not possible, with only a python client, but I'm seeing that there are more portable implementations now, so I'll probably have to give it a try again when I have time to waste for this (to be clear, between working on HTTP/2 and playing again with SSL toys, my choice is clearly in favor of the one making the project go forward). Thanks for notifying me! Willy

