🚨🚨🚨 5 minutes until the Let's Encrypt R3 intermediate expires 🚨🚨🚨
29 September 2021 19:21:40 UTC
TANGO DOWN 😅
Are we still here?
I just refreshed the page on my Chrome/Windows 10 Pro install and it automatically built a new certificate chain around the expired intermediate! It's awesome when it works 😎
The problem is clients that don't have this option available are now possible seeing certificate errors on connections. Let's see if any reports surface...
If something didn't already go kablam, the DST Root CA X3 expires in a little over 18 hours, then you're free and clear!
Sep 30 14:01:15 2021 UTC
I'm getting reports of issues on devices where we didn't expect any problems... Please report any issues you're seeing on this thread 👍
A fix for Android versions >=7.1.1 if you're seeing errors for the expired R3 intermediate certificate is to kill your running apps and reboot the device.
I now have multiple reports that Bluecoat and Palo Alto proxies encountering the expired R3 intermediate will fail and refuse to connect. Even if you have a modern client behind one of these proxies that could otherwise work around the issue, those sites will be unreachable.
Unconfirmed: Cisco Umbrella Secure Gateway Web Proxy is currently reporting service issues that started ~the same time as the intermediate expiry. Looking for confirmation the two events are related: status.umbrella.com/#/detail/582
There are also many reports of iOS and macOS versions newer than expected seeing issues on sites serving the expired R3 intermediate. I've seen errors on iOS 11, 13 and 14 along with several macOS version only a few minor releases behind current. No fix on the client side yet.
🚨🚨🚨 14 hours until the IdenTrust DST Root CA X3 expires! 🚨🚨🚨
Sep 30 14:01:15 2021 UTC
Issues likely being caused by bad certificate chains are starting to surface, Catchpoint have a incident open: status.catchpoint.com/incidents/f5yl…
The @guardianiosapp (Guardian Firewall) is currently experiencing an outage:
I've created a test site to help identify issues with clients. If you can connect to expired-r3-test.scotthelme.co.uk then your client can handle being served the expired R3 Intermediate in the server chain!
As you can see, my Chrome on Windows 10 is able to build an alternate trust path through the valid R3 Intermediate to the ISRG Root X1:
Using openssl s_client or similar you can see that the sever is ending the expired R3 Intermediate in the chain:
Of course, @ssllabs is also detecting that my chain is invalid and showing the alternate, valid chain that can be built: ssllabs.com/ssltest/analyz…
It seems that Fortinet are also having issues with Fortigate (the Next Generation Firewall) old.reddit.com/r/fortinet/com…
Many reports of issues connecting to Heroku API endpoints, but status pages doesn't seem to indicate any but metrics is broken right now: status.heroku.com
InstaPage also has an active incident where the timeline fits for it to be certificate related: status.instapage.com
To clarify, I understand people needing to do this now to make stuff work, it's how many people will forget to change the setting back that worries me.
I bought a phone from a large retailer here in the UK and they shipped a faulty unit. These things happen, so I return it for a refund and they got it on 6th Aug:
They had no other phones of the same spec anyway so they said they were going to refund me. By 13th Aug, still no refund.
I chased a couple more times and by 14th Sep, still no refund! They say it will now take them 3-5 days to issue a refund:
Are you using CSP on your website? You might be getting a patent infringement notice! Buckle up 😎 scotthelme.co.uk/i-turned-on-cs…
We're already working with the @EFF who will hopefully be able to support the cause here, but we need to know about other websites that have received this letter.
If you're legally and/or technically minded, perhaps you could take a look over the letter being sent out: drive.google.com/file/d/1p63IJ6…
1) Shorter passwords are easier to remember which is what makes them weak and easy to guess. This means it's more likely someone else will have access to it, not less likely.
@BritishGasHelp@srobertson92 2) Allowing someone to have an easy to remember 8-10 character password doesn't mean you need to prevent someone else from having an ultra-secure 64 character password. It's possible for both of these things to coexist, and they should.
@BritishGasHelp@srobertson92 3) Weak passwords do not protect customer data, they do the opposite and put customer data at risk. We should be encouraging stronger passwords and the use of password managers.
There's been a lot of discussion about OCSP again recently after the Apple incident caused by Big Sur. I've written up some details about what happened and thoughts for what we could/should do about it: scotthelme.co.uk/deja-vu-macos-…
Apple published a support article to address the concerns raised, here are the details and my update based on their comments: scotthelme.co.uk/deja-vu-macos-…
Apple will introduce "A new encrypted protocol for Developer ID certificate revocation checks" but are we talking OCSP over HTTPS or something else?