Expired Server Certificate Handled As Client Clock Error

Description of the issue:

This is potentially a duplicate of Certificate error wrongly suggests system clock is ahead , which describes the same issue I’m observing on macOS, except on Android. When browsing a site with a recently expired server certificate, Brave instead reports that the client’s clock is incorrect.

Exact URL of the website in question:

https://cmake.org/

Did the issue present with default Shields settings? (yes/no)

I don’t know, because that link does not appear to document how to reset Shield settings to the default.

Does the site function as expected when Shields are turned off?

No, there is no change when Shields are turned off for the site.

Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration. (yes/no):

Not that I am aware of.

Does the site work as expected when using Chrome?

Yes, Chrome reports the certificate is recently expired, and does not assume it is a client clock error.

Brave version (check About Brave):

Version 1.25.68 Chromium: 91.0.4472.77 (Official Build) (x86_64)

Screenshots


2 Likes

Thanks, that’s definitely a bug. I have filed an issue for it:

4 Likes

I am experiencing the same issue on Desktop, Windows 10, for a website called aidchain.co

There is nothing wrong with my clock.

Version 1.25.68 Chromium: 91.0.4472.77 (Offizieller Build) (64-Bit)