mirror of
https://github.com/saymrwulf/xous-core.git
synced 2026-11-17 08:40:52 +00:00
This allocates some additional one way counters dedicated to hardening: - Paranoid mode is duplicated in slots 65 & 67 - An attack counter is in slot 66 - Redundant revocation counters are seated in slot 68 The primary revocation counters are in slot 116. This means that cutting out the revocation counters would probably require at least two edits to the memory array - simply cutting the word addressing line for those columns might be enough to defeat a counter. Paranoid mode duplicate is stored somewhat close to the primary counter, which means it could be subject to a single line cut to fully defeat the counter, but the space is getting pretty crowded so I'll leave it like that; I really want to leave the bottom 64 slots available for application use. A "flag" key is allocated, plus a dummy flag is committed to the repo. This is a value that, if retrieved, would ostensibly bring the retriever glory and bounty, to the extent that any glory or bounty is to be had (ps: I'm poor and this project is obscure). The actual flag, of course, is not in the repo...I hope! The flag value is different from all other values in that this is the only shared, common secret across all devices. All other device secrets are generated on a per-device basis from the TRNGs. So the flag needs some special treatment such that it's not overwritten during device keying. The flag exists because I'm hoping that anyone who manages to extract it will also provide a helpful explanation of the procedure to get it out, so that the system could be patched (if the error is patchable) or rev'd in future silicon. That being said, a flag retrieval is not necessarily equal to a full break of security across all devices because as mentioned above, most device secrets are on a per-device basis. The flag represents then, the amount of effort necessary to apply to every device to retrieve the secrets within.
32 B
32 B