New issue
Advanced search Search tips

Issue 917607 link

Starred by 3 users
Status: Assigned
Owner:
jdeblasio@chromium.org
Cc:
phanindra.mandapaka@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug
Team-Security-UX



Sign in to add a comment

Privacy error page for NET::ERR_CERT_DATE_INVALID incorrectly calculates when certificate expired

Reported by adunk...@gmail.com, Dec 22 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36

Steps to reproduce the problem:
1. Go to a site with a recently expired certificate (within the last hour, not sure if that’s important).

What is the expected behavior?
The text should state that the certificate expired today.

What went wrong?
The text states that the certificate expired yesterday.

Did this work before? N/A 

Chrome version: 70.0.3538.110  Channel: stable
OS Version: OS X 10.14.2
Flash Version:
DvDmOeIX4AEfYH3.jpg
151 KB View Download

Comment 1 by adunk...@gmail.com, Dec 22 

Should have included my system clock in that screenshot, but the screenshot was taken at 6:01PM EST on December 22nd.

Comment 2 by swarnasree.mukkala@chromium.org, Dec 23

Labels: Needs-Milestone

Comment 3 by phanindra.mandapaka@chromium.org, Dec 26

Cc: phanindra.mandapaka@chromium.org
Components: -UI Internals>Network>Certificate
Labels: Triaged-ET
Thanks for filing the issue...

As per comment #0, tried to reproduce the issue on reported chrome 70.0.3538.110 using Mac 10.14.0 with provided url in the attachment https://cdn1.venmo.com/ as we are getting XML code and the issue related to site with a recently expired certificate. Hence, requesting someone from Internals>Network>Certificate team to look into it.

Thanks..!
917607.PNG
14.8 KB View Download

Comment 4 by sleevi@google.com, Dec 26

Components: -Internals>Network>Certificate UI>Browser>Interstitials
Labels: OS-Android OS-Chrome OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Redirecting, as its an interstitials issue. As mentioned in the original description, this would only manifest with a recently expired certificate; testing several days later would thus not be expected.

The issue is in the IDS_CERT_ERROR_EXPIRED_DETAILS, which rounds up (so that 1 hour becomes 1 day instead of 0 days), and thus results in "yesterday".

Comment 5 by jdeblasio@chromium.org, Jan 4

Labels: -Pri-2 Pri-3
Owner: jdeblasio@chromium.org
Status: Assigned (was: Untriaged)
►

Sign in to add a comment