First up, I want to pass along a big “thank you” from the folks who manage our CT infrastructure. Your bug let them quickly identify the root cause of this issue, which is a configuration problem at our end O-: The timing of this is a bit tricky. I can’t predict the future, obviously, but there may be a short window (weeks not months) between the release of iOS 26 and the release of this fix where your customers are affected by the issue. If that’s likely to cause you significant grief, you’ll need a workaround. To understand the workaround I need to explain a little bit about the bug… The bug you’ve found means that iOS won’t trust certificates issued by your CA in the 8 hours between 2026-07-01 00:00:00 GMT and 2026-07-01 08:00:00 GMT. And lo! your server’s certificate just happens to expire in that range: % openssl x509 -inform der -in leaf.cer -text … Validity Not Before: May 30 06:03:02 2025 GMT Not After : Jul 1 06:03:01 2026 GMT … That’s just bad luck )-: The workaround is to ask your CA to is
Topic:
Privacy & Security
SubTopic:
General
Tags: