security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

clarify factory images flashing improvement

Browse Source
This commit is contained in:
Daniel Micay 2022-08-31 00:53:56 -04:00
parent aaa600dbd4
commit a9ddbf2379
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
static/releases.html
View File

@ -602,7 +602,7 @@
<li>add per-app toggle to relax memory corruption exploit protections for an app to allow users to work around buggy apps with latent bugs including many games like Diablo Immortal (uses 39-bit address space and Scudo instead of 48-bit address space and hardened_malloc along with forcing exec spawning for the app since the Zygote is always fully hardened)</li>
<li>Sandboxed Google Play compatibility layer: expand existing shims to further improve compatibility</li>
<li>improve infrastructure for GrapheneOS package state</li>
<li>improve safety of factory images flashing scripts by flashing the SoC firmware to the inactive slot, switching to it and then flashing it to the previously active slot before proceeding with flashing the OS (this provides a high level of safety for devices like 6th generation Pixels doing boot chain anti-rollback despite the fact that they neglected to provide firmware handling flashing safely)</li>
<li>improve safety of factory images flashing scripts by flashing the SoC firmware to the inactive slot, switching it to active, rebooting to it and then repeating the same thing against to get the current firmware flashed on both slots and boot tested (this provides a high level of safety for devices like 6th generation Pixels doing boot chain anti-rollback despite the fact that they neglected to provide firmware handling flashing safely)</li>
<li>Pixel 6, Pixel 6 Pro, Pixel 6a: erase DPM partitions in factory images flashing scripts</li>
<li>drop unused flash-base.sh from factory images to reduce maintenance burden for our safer flashing procedure</li>
<li>System Updater: catch ServiceSpecificException thrown by UpdateEngine.applyPayload(...) in some cases to properly report the error via a notification</li>