I can confirm that upgrading to 158.0.2 fixed it for me (I tested right before the update and it was still trusting the corresponding CA, and after updating it doesn’t anymore).
I thought 158.0.1 is supposed to have the knowledge of these certificate revocations hard-coded? Maybe I misunderstood what the point of the browser update was.
I installed 158.0.1, restarted my phone, opened the website, waited long enough that the screen of my phone turns off, then reloaded the page. It still says “connected”.
I’m also on
158.0.1(Samsung Galaxy S26 Ultra, Android 17) and restarting my phone didn’t fix it.score 1 · canonical
Thanks for the message. We found the bug. See response above.
score 1 · canonical
I can confirm that upgrading to
158.0.2fixed it for me (I tested right before the update and it was still trusting the corresponding CA, and after updating it doesn’t anymore).score 1 · canonical
I thought 158.0.1 is supposed to have the knowledge of these certificate revocations hard-coded? Maybe I misunderstood what the point of the browser update was.
I installed 158.0.1, restarted my phone, opened the website, waited long enough that the screen of my phone turns off, then reloaded the page. It still says “connected”.
score 1 · canonical
Yeah there was another independent bug. You should update to
.2score 1 · canonical
That finally fixed it, thanks :)
score 1 · canonical