Issue metadata
Sign in to add a comment
|
SCT timestamp shown in DevTools is incorrect |
||||||||||||||||||||||||||
Issue descriptionGoogle Chrome 66.0.3359.181 (Official Build) (64-bit) (cohort: Stable) Revision a10b9cedb40738cb152f8148ddab4891df876959-refs/branch-heads/3359@{#828} OS Windows What steps will reproduce the problem? (1) Open Chrome Developer Tools (2) Switch to Security panel (3) Navigate to https://bbc.co.uk (4) Click on "https://www.bbc.co.uk" under "Main origin" on the Security panel (5) Click "Show full details" under "Certificate Transparency" (6) Observe the signed certificate timestamps, specifically the "issued at" date What is the expected result? Date is in the past What happens instead? Date is in the far future (the year 2387). This bug does not appear on a Chromebook at version 63.0.3239.140 (Official Build) (64-bit).
,
May 23 2018
This bug does not appear to be specific to certain websites - I've tried a few (e.g. google.com) and see SCTs supposedly issued in the year 2387 for all of them.
,
May 23 2018
1) Can you include screen shots? 2) Can you include net-internals? When I attempt to reproduce, loading "https://bbc.co.uk" under canary redirects me to http://www.bbc.com (yay for site-specific geocentrism! and http://), so I'm not able to diagnose from here. I suspect there could be some interplay with the disk cache here (and more specifically, that we don't load SCTs from it), but without a net-internals, it'll be tricky to diagnose.
,
May 23 2018
Using Version 68.0.3438.0 (Official Build) canary (64-bit) on Windows, I am unable to reproduce this, accessing SCT-serving sites in a new, existing, or incognito profile.
,
May 23 2018
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by robpercival@chromium.org
, May 23 2018