dasharo/docs
0
0
Fork 0
mirror of https://github.com/Dasharo/docs.git synced 2026-06-13 10:16:57 -07:00
Code Issues Packages Projects Releases Wiki Activity

docs/guides/redundancy.md: use trustroot names

Browse Source 
Signed-off-by: Michał Kopeć <michal.kopec@3mdeb.com>
This commit is contained in:
Michał Kopeć
2026-03-31 15:11:21 +02:00
parent 81b5ab4fab
commit 41a2f44f70
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guides/redundancy.md
+3 -3
View File
@@ -47,7 +47,7 @@ This command sequence writes the new firmware image into the appropriate regions
`attempt_slot_b` CMOS option to "Enable". This ensures that after the next
reboot, the system will boot from the newly updated slot.
## Security: Chain of Trust with Intel Boot Guard and CBFS Verification
## Security: Chain of Trust with TrustRoot and CBFS Verification
### Slot Integrity via CBFS Verification
@@ -57,9 +57,9 @@ is checked before it is loaded. This ensures that any corruption or tampering
within a slot is detected before the affected code runs, regardless of which
slot is active.
### Intel Boot Guard Integration
### Dasharo TrustRoot Integration
When Intel Boot Guard is enabled, it extends the root of trust into hardware.
When TrustRoot is enabled, it extends the root of trust into hardware.
On every boot, the Boot Guard ACM — executed directly by the CPU before any
firmware code runs — cryptographically verifies the **bootblock** of the active
slot. Because the bootblock in turn holds the CBFS hashes, a single hardware