SoylentNews is people
SoylentNews
from the honestly,-it's-for-your-own-good... dept.
Safari will, later this year, no longer accept new HTTPS certificates that expire more than 13 months from their creation date. That means websites using long-life SSL/TLS certs issued after the cut-off point will throw up privacy errors in Apple's browser.
The policy was unveiled by the iGiant at a Certification Authority Browser Forum (CA/Browser) meeting on Wednesday. Specifically, according to those present at the confab, from September 1, any new website cert valid for more than 398 days will not be trusted by the Safari browser and instead rejected. Older certs, issued prior to the deadline, are unaffected by this rule.
By implementing the policy in Safari, Apple will, by extension, enforce it on all iOS and macOS devices. This will put pressure on website admins and developers to make sure their certs meet Apple's requirements – or risk breaking pages on a billion-plus devices and computers.
[...] Shortening the lifespan of certificates does come with some drawbacks. It has been noted that by increasing the frequency of certificate replacements, Apple and others are also making life a little more complicated for site owners and businesses that have to manage the certificates and compliance.
"Companies need to look to automation to assist with certificate deployment, renewal, and lifecycle management to reduce human overhead and the risk of error as the frequency of certificate replacement increase," Callan told us.
We note Let's Encrypt issues free HTTPS certificates that expire after 90 days, and provides tools to automate renewals, so those will be just fine – and they are used all over the web now. El Reg's cert is a year-long affair so we'll be OK.
GitHub.com uses a two-year certificate, which would fall foul of Apple's rules though it was issued before the cut-off deadline. However, it is due to be renewed by June, so there's plenty of opportunity to sort that out. Apple's website has a year-long HTTPS cert that needs renewing in October.
Microsoft is an interesting one: its dot-com's cert is a two-year affair, which expires in October. If Redmond renews it for another two years, it'll trip up over Safari's policy.
(Score: 3, Interesting) by driverless on Tuesday February 25 2020, @11:11AM (4 children)
Doesn't work because it would break all Internet sites with correct times because cert, CRL, and OCSP times would be out. Another cool security feature, your clock is off so the CRL is future-dated so we'll assume the cert is invalid and won't let you connect. Or at least Firefox does that.
(Score: 2) by Pino P on Tuesday February 25 2020, @02:28PM (3 children)
Then use one clock setting to connect to SCADA and a different clock setting to connect to public websites.
(Score: 3, Informative) by tangomargarine on Tuesday February 25 2020, @03:43PM (2 children)
We're going off into the weeds here. The far simpler solution is for Safari to not be dumb.
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
(Score: 2) by Pino P on Tuesday February 25 2020, @08:45PM (1 child)
"To not be dumb" is a tall task for Safari or any other proprietary or tivoized software.
(Score: 2) by driverless on Tuesday February 25 2020, @11:24PM
Or for security people in general. Security people are supposed to provide guide rails, but most of the time they just make a roadblock.