Issue metadata
Sign in to add a comment
|
oobe: dev-chromium starts owning the device before the 1st login (prod chrome is fine) |
||||||||||||||||||||||
Issue description[Triggered by comments in https://crrev.com/c/688763] After https://crrev.com/c/688763, on devices with dev build of Chromium, taking the ownership starts as soon as the device is booted for the 1st time/after powerwash, not waiting for the first login. Revert the behavior back to the original.
,
Jan 6 2018
,
Feb 14 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/cd8739419b6be0cd53e7f116fb584579c2d88e61 commit cd8739419b6be0cd53e7f116fb584579c2d88e61 Author: Andrey Pronin <apronin@chromium.org> Date: Wed Feb 14 18:54:12 2018 Don't auto-own the tpm on the first Chromium boot. For Chromium builds, instead of triggering tpm ownership on boot, rely on it being triggered after the first login (as it was before CL:688763). after booting, (b) the tpm is owned after logging in. Bug: 799664 Test: clear the owner, reboot, verify that (a) the tpm is not owned Change-Id: I991333e0f049c998dc126827dc141419bf1c3503 Reviewed-on: https://chromium-review.googlesource.com/917537 Reviewed-by: Alexander Alekseev <alemate@chromium.org> Commit-Queue: Andrey Pronin <apronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#536764} [modify] https://crrev.com/cd8739419b6be0cd53e7f116fb584579c2d88e61/chrome/browser/chromeos/chrome_browser_main_chromeos.cc
,
Mar 5 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by apronin@chromium.org
, Jan 6 2018