bunnie 26078dcc7d add keystore to dabao configuration ... After some contemplation, we should include the keystore in the core service set featured by the dabao-xous configuration. The pros are: any compatibility/sharing of resources that require access to RRAM, one-way counters, UUIDs, etc. will either require a wholly separate implementation that is "insecure" or it could just reuse the baosec work. Furthermore, as cryptographic accelerators are laid into the keystore, the APIs become available to the dabao environment The cons are: more space is used in a space-constrained dabao environment (roughly 140k "deadweight" at the start, but as cryptographic APIs get layered in this can grow substantially); the key slots are "used up" in part by the scheme, which leaves less key slots available for user-defined purposes. This is mitigated by the fact that there are a couple thousand key slots, and so even though we use a couple hundred of them it's still not the whole range. Also, the baosec/dabao feature flag can be used to feature-out cryptographic APIs/accelerators that are too obscure or not useful for the dabao environment, to "lighten up" the firmware load.		2025-11-01 22:59:07 +08:00
..
src	add keystore to dabao configuration	2025-11-01 22:59:07 +08:00
Cargo.toml	bump versions	2025-10-06 13:23:18 +08:00