From 1eeaa2351667894897a03041a69b462e5a64bc45 Mon Sep 17 00:00:00 2001 From: bunnie Date: Mon, 20 Oct 2025 23:36:34 +0800 Subject: [PATCH] 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. --- bao1x-boot/boot0/src/platform/bao1x/bao1x.rs | 7 ------- 1 file changed, 7 deletions(-) diff --git a/bao1x-boot/boot0/src/platform/bao1x/bao1x.rs b/bao1x-boot/boot0/src/platform/bao1x/bao1x.rs index a370df238..681cb816f 100644 --- a/bao1x-boot/boot0/src/platform/bao1x/bao1x.rs +++ b/bao1x-boot/boot0/src/platform/bao1x/bao1x.rs @@ -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 = {