TPM firmware update flow via chrome://chrome doesn't work for enrolled devices |
||
Issue descriptionRepro steps: 1. enroll device, enable the allow_user_initiated_powerwash setting in device policy 2. sign in, go to chrome://chrome on non-updated device (or fake via putting /run/tpm_firmware_update_available in place) 3. Click the line item, confirm restart Observe that nothing happens. The reason is that BrowserLifetimeHandler::HandleFactoryReset is missing a check for the case when TPM firmware updating is allowed per policy. I swear I had added this code at some point, but it somehow got lost... I'll send a fix.
,
Jan 31 2018
,
Feb 26 2018
Can this be merged? I'm unable to get a new cert because I need to update TPM firmware first. I can't update my TPM firmware because I'm on 63 and the powerwash flow doesn't work. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Dec 8 2017