tpm: owned/enabled sysfs attributes should be exposed for tpm2 in kernel-4.12 |
|||
Issue descriptionUserland scripts (e.g. factory) rely on tpms exposing 'enabled' and 'owned' attributes through sysfs. See b/35576018. chromeos-4.12 currently doesn't have anything similar to https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/362383 . So, those attributes should be created. Alternatively, scripts should be modified to get this information through other channels if sysfs doesn't contain this info.
,
Sep 11 2017
,
Sep 11 2017
apronin@: I am confused. Are you saying I got something wrong when applying "CHROMIUM: tpm: add legacy sysfs attributes for tpm2" to chromeos-4.12 ? This is the list of tpm sysfs attributes on eve (from /sys/class/tpm/tpm0), running chromeos-4.12. dev:10:224 disable_clear:0 eh_enable:1 enabled:1 endorsement_auth_set:1 in_lockout:0 lockout_auth_set:1 lockout_counter:0 lockout_interval:1000 lockout_recovery:1000 max_auth_fail:200 orderly:1 owned:1 owner_auth_set:1 ph_enable:0 ph_enable_nv:1 sh_enable:1 timeouts:750000 2000000 750000 750000 [original] tpm_generated_eps:1 uevent:MAJOR=10 uevent:MINOR=224 uevent:DEVNAME=tpm0 What is wrong/missing ?
,
Sep 11 2017
False alarm, looked at the wrong branch. My bad. |
|||
►
Sign in to add a comment |
|||
Comment 1 by apronin@chromium.org
, Sep 11 2017