5 ms·
Interesting. That's an (expired) Cloudflare certificate, and those are Cloudflare IP addresses I'm being sent to. I wonder if Cloudflare broke this somehow (wh
by tialaramex 5y ago
Interesting. That's an (expired) Cloudflare certificate, and those are Cloudflare IP addresses I'm being sent to.
I wonder if Cloudflare broke this somehow (whoops) or if Thunderbird themselves screwed up here. I don't see a CAA record that would tell DigiCert they can't issue this either.
- xPaw 5y agoIt is indeed Cloudflare, very strange. > curl -k https://addons.thunderbird.net/cdn-cgi/trace https://addons.thunderbird.net/cdn-cgi/trace
- Namidairo 5y agoLooks like Lets Encrypt R3 to me, with a very recent issuance time. Resolved, probably?
- zinekeller 5y agoYes. Okay, is DigiCert having problems today? That's CloudFlare's primary provider, so the LE certificate might be a stop-gap applied by CF.
- tialaramex 5y agoBut that's a much bigger problem that it might appear. If Cloudflare gets right to the wire and then is like "Oh, DigiCert couldn't issue for whatever reason" then that's a process problem at Cloudflare not DigiCert. A reasonable strategy is to renew say, 30 calendar days in advance. But that would mean Cloudflare (or at least, some automated system that nobody was looking at) knew 30 days ago this would happen and nothing was done about it.
- wila 5y agoPerhaps that's why it was broken? I only see certificate issuances from Let's Encrypt. https://crt.sh/?q=addons.thunderbird.net https://crt.sh/?q=addons.thunderbird.net
- tialaramex 5y agoThe Cloudflare certificate which expired was for *.thunderbird.net which you will be able to find in crt.sh for yourself - and was issued a year ago under Cloudflare's intermediate† None of those R3 certificate expire today, and the expired cert I was originally served when this was a fresh news item was from that Cloudflare intermediate CA under DigiCert. It's possible that normally Thunderbird has Cloudflare trust their backends via the Let's Encrypt certificate rather than using Cloudflare's private "origin" CA for that purpose. That would give them the flexibility to cut Cloudflare out of the loop if necessary. But what exactly happened here I expect we'll learn in a post-mortem. † I assume but don't know for certain that in fact DigiCert operates this intermediate CA simply on behalf of Cloudflare but entirely on their own premises and with them ensuring its obeys the CA/B BRs and other trust store policies. I think the idea of letting somebody else operate unconstrained intermediates with them doing all the work died out after it sank Symantec.
- wila 5y agoAhh yes that makes perfect sense, thanks. I do indeed see the Cloudflare one from a year ago. Seems it was now renewed as a Let's Encrypt one.
- swiley 5y agoSo you're really trusting Cloudflare and not Mozilla but no one using the MUA is really told that. Why bother encrypting anything at this point of the connections are going to be terminated somewhere in the network anyway?
- tialaramex 5y agoMozilla decided to trust Cloudflare. So you're still just trusting Mozilla. Companies have lots of suppliers.