#Turbo boost switcher big sur not working android#
But there's still a good number of Android (and other) devices out there that have never been updated and will thus be locked out. There is a strong push to get rid of TLS 1.2 because it's no longer strong enough. Obviously the 20-year-old browser usecase is not a compelling one, but you don't have to go this far back. Maybe in the US it's normal for ISPs to meddle with their user's traffic, but other than that it is extremely unlikely that anyone in the middle can see, let alone change the data you are requesting. (I think that's the only case where Safari prompts you to add a permanent exception self-signed and wrong-domain certs just have a click-through warning and most actual errors can't be bypassed at all.)
That doesn't really excuse Safari's ass-backwards certificate expiration behavior, though. Let's Encrypt means it's free and easy, and if Certbot + nginx/apache is too much setup for you, there are servers out there now that'll automate it away completely. Unless you're building a website specifically targeted to people running browsers from 1999, there's really no reason to not have TLS on your site these days. That, plus there are browser features locked behind HTTPS now, plus it keeps your ISP from seeing what specific content you're looking at (they likely can see which sites you're visiting on a broad level either way because of DNS and SNI in cleartext). With services like Let’s Encrypt and easy automation, there’s no reason sites should have expired certificates anymore (and yet it still happens…). The reason why people advocate encrypting everything is to prevent middle-boxes from tampering with them. As far as I know, there is no way to bypass it just once. Safari adds the certificate to your certificate store, which is why it requests authorization.