Issue metadata
Sign in to add a comment
|
Chrome OS should ensure clock sync before first-run experience |
||||||||||||||||||||||||
Issue descriptionChrome Version: 44 Chrome OS Platform: Chromebook Flip Steps To Reproduce: (1) Unbox new Chromebook Flip (2) Start out-of-box setup Expected Result: No error Actual Result: Blocked by Certificate Error How frequently does this problem reproduce? It reproduced only because the system clock was incorrect, and the dialog was shown (and errored) before network time sync fixed it. User Impact: Confusion, annoyance. Workaround: Wait for network time sync. Reload page.
,
Mar 28 2016
rtc, pstew: Who owns the network time service (tlsdated) on CrOS? I suspect to reasonably accomplish this (improving the OOBE), we want to either block the OOB flow on getting a DBus signal from the time service (I thought we did, at one point?), or at least surface this information up as a signal that Chrome can listen to/react to. It does seem that the 'best' OOBE would be to add a direct phase indicating time is being sync'd, and to let the user confirm the date/time, prior to continuing installation, matching the OOBE of a number of other consumer devices.
,
Mar 29 2016
As I understand it wad@ did a fair amount of work on tlsdated. I don't know who if anyone on the Chrome OS team inherited it from him.
,
Mar 30 2016
It's possible that something was changed here between CrOS 44 and CrOS 46? I ended up replacing my Flip and my new one was manufactured two months later and came with Cr46 by default. When I first booted and entered the out-of-box experience, the system date was November 5, 2015, which is before the certificate validity date of accounts.google.com. However, unlike last time when I got a cert error page, this time I got a white dialog box with a spinning "Please wait"; periodically, there was a 50ms flash of some other screen (it looked like it had the network error dinosaur on it); when those stopped, the Please Wait page turned into the working login page and the system clock had been fixed.
,
Jun 7 2016
Sign in flow changed in M46. It's possible some check was lost along the way.
,
Nov 22 2016
,
Nov 10 2017
,
Feb 18 2018
,
Nov 9
Yep lots of changes here, I think this is obsolete. Please reopen if seen again. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by f...@chromium.org
, Mar 28 2016Components: Security>UX