New issue
Advanced search Search tips

Issue 701151 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Investigate possibility of failure to verify install attributes

Project Member Reported by tnagel@chromium.org, Mar 13 2017

Issue description

apronin has pointed out that devices get into an undefined state when the TPM gets cleared but the disk is not cleared.  We should investigate whether that's happening in the wild.  Do we have UMA?  If not, it might make sense to instrument InstallAttributes::SetIsInvalid() (or one of its callers) to see how often install attributes fail to be verified.

https://cs.corp.google.com/chromeos_public/src/platform2/cryptohome/install_attributes.cc?sq=p:chromeos_public&dr=CSs&l=70
 
Just to be clear, it happened in practice for pre-production devices. But in that case it was planned: the tpm nvram was deliberately cleared as a part of the update process. Shouldn't happen in the wild (unless there are bugs in tpm firmware or some electric glitches, of course). Still, if it does happen, that'd be good to know.
Components: OS>Systems>Security
Do we still want this?

Sign in to add a comment