No description
74997ed800
KeyMint spec requires unique ID rotation to happen every 30 days (or more precisely 2592000000 milliseconds) starting at UNIX epoch time. Keystore is also supposed to set the RESET_SINCE_ID_ROTATION to indicate "whether the device has been factory reset since the last unique ID rotation". However, instead Keystore sets RESET_SINCE_ID_ROTATION if there has been a factory reset in the last 30 days counting back from now, which is different and will give one extra UNIQUE_ID value in a subsequent period: For example, if there's a factory reset (marked as :) in the 3rd period (periods delimited by |), the first half of the 4th period will have RESET_SINCE_ID_ROTATION set and get a different UNIQUE_ID value than it should: Want = | A | B | C : C2 | D | ... Get = | A | B | C : C2 | D2 : D | ... Bug: 289774200 Test: keystore2_test Change-Id: I156de902931915cd1ae7ad2eba63fd0276f15ae0 |
||
|---|---|---|
| diced | ||
| fsverity | ||
| fsverity_init | ||
| identity | ||
| keystore | ||
| keystore-engine | ||
| keystore2 | ||
| ondevice-signing | ||
| prng_seeder | ||
| provisioner | ||
| .clang-format | ||
| .gitignore | ||
| Android.bp | ||
| METADATA | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||
| OWNERS | ||
| PREUPLOAD.cfg | ||
| rustfmt.toml | ||