firmware anti-rollback is actively used since Pixel 6

This commit is contained in:
Daniel Micay 2024-08-06 13:12:28 -04:00
parent 02ad1d7518
commit 03be1b8687
2 changed files with 6 additions and 6 deletions

View File

@ -556,9 +556,9 @@ curl -O https://releases.grapheneos.org/<var>DEVICE_NAME</var>-install-<var>VERS
OS, it can be detected with these features.</p>
<p>Verified boot verifies the entirety of the firmware and OS images on every
boot. The public key for the firmware images is burned into fuses in the SoC
at the factory. Firmware security updates can also update the rollback index
burned into fuses to provide rollback protection.</p>
boot. The public key for the firmware images is burned into fuses in the SoC at
the factory. Firmware security updates also update the rollback index burned
into fuses to provide rollback protection.</p>
<p>The final firmware boot stage before the OS is responsible for verifying
it. For the stock OS, it uses a hard-wired public key. Installing GrapheneOS

View File

@ -360,9 +360,9 @@
OS, it can be detected with these features.</p>
<p>Verified boot verifies the entirety of the firmware and OS images on every
boot. The public key for the firmware images is burned into fuses in the SoC
at the factory. Firmware security updates can also update the rollback index
burned into fuses to provide rollback protection.</p>
boot. The public key for the firmware images is burned into fuses in the SoC at
the factory. Firmware security updates also update the rollback index burned
into fuses to provide rollback protection.</p>
<p>The final firmware boot stage before the OS is responsible for verifying
it. For the stock OS, it uses a hard-wired public key. Installing GrapheneOS