From 036e75e5421caa3f8b23ef9b42b74cc794e122a6 Mon Sep 17 00:00:00 2001 From: Adam Joseph Date: Thu, 30 Mar 2023 01:19:10 -0700 Subject: [PATCH] README.md: link to more details about ecfw write protection --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b31dd89..c6c0226 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,7 @@ See [doc/architecture.md](doc/architecture.md). * This project was originally inspired by the [petitboot](http://jk.ozlabs.org/projects/petitboot/) kexec-based bootloader, a [derivative of which](https://wiki.raptorcs.com/wiki/Petitboot) is shipped with Raptor Computing's POWER9 hardware. -* The independent write protection of normal/fallback images was inspired by a [similar scheme](https://chromium.googlesource.com/chromiumos/platform/ec/+/HEAD/docs/write_protection.md) used by the Embedded Controller firmware in arm64 Chromebooks. +* The independent write protection of normal/fallback images was inspired by a [similar scheme](https://chromium.googlesource.com/chromiumos/platform/ec/+/HEAD/docs/write_protection.md) used by the Embedded Controller firmware in arm64 Chromebooks. [More details](https://chromium.googlesource.com/chromiumos/platform/ec/+/HEAD/docs/write_protection.md#ro-and-rw). * The nix language is, *by far*, the most advanced solution available for auditable and reproducible builds of complex software. An incredible amount of software goes into an ownerboot image (almost none of which was written by me!); it's effectively a tiny Linux distribution, and as a bootloader it is at the pinnacle of security sensitivity. Nothing else besides nix gave me any confidence that I knew what was going into my bootloader.