mirror of
https://github.com/saymrwulf/xous-core.git
synced 2026-11-13 07:48:30 +00:00
8dc1e9c837
a slice of key material is written to backup RAM from boot0 all the way to the loader, to prove to the loader that secret keys were erased in a higher privilege state (loader then erases the key, and this key is considered leakable without harm to security). The problem is that writing the key to backup RAM in boot0 was fixing the hash on the backup block, which is before the check happens to see if it was a cold power-on. This would defeat the RTC setting & backup setup logic. THe solution to this is to exclude that one key from the hashing area and special case it. A set of routines and API names were added to help enforce this case. |
||
|---|---|---|
| .. | ||
| bao1x-api | ||
| bao1x-hal | ||
| blitstr2 | ||
| chat | ||
| cos_table | ||
| flatipc | ||
| flatipc-derive | ||
| keystore-api | ||
| mass-storage | ||
| perflib | ||
| precursor-hal | ||
| tls | ||
| userprefs | ||
| ux-api | ||
| xous-bio | ||
| xous-bio-bdma | ||
| xous-pio | ||
| xous-pl230 | ||