mirror of
https://github.com/saymrwulf/xous-core.git
synced 2026-11-16 08:38:26 +00:00
Realizing that the permission level settings could change
Not locking them down in boot0: allowing them to be set up in boot1. this is less hermetic, but already I have thought of a couple of reasons to modify the tables; for example, the dabao configuraiton if someone wanted to make a secured version, you might not want PID 3 to be the trusted PID; or if you wanted to have two different sets of keys for different purposes, you can use the other permission levels to separate them. So, leaving it configurable. for now.
This commit is contained in:
parent
2095acfe13
commit
1eeaa23516
1 changed files with 0 additions and 7 deletions
|
|
@ -105,13 +105,6 @@ pub fn early_init() {
|
|||
// malleable (no hardware lock to prevent update), which is a potential vulnerability.
|
||||
init_hash();
|
||||
|
||||
// this is a security-critical initialization. Failure to do this correctly breaks
|
||||
// the hardware access control scheme for key/data slots.
|
||||
let mut cu = bao1x_hal::coreuser::Coreuser::new();
|
||||
// safety: this is safe because it's followed by a `protect()` call.
|
||||
unsafe { cu.set() };
|
||||
cu.protect();
|
||||
|
||||
// TxRx setup
|
||||
#[cfg(feature = "unsafe-dev")]
|
||||
let mut udma_uart = {
|
||||
|
|
|
|||
Loading…
Reference in a new issue