diff options
| author | Daniel Micay <daniel.micay@grapheneos.org> | 2024-07-31 21:05:51 -0400 |
|---|---|---|
| committer | Daniel Micay <daniel.micay@grapheneos.org> | 2024-07-31 21:05:51 -0400 |
| commit | 6c25b49460b0b05979ff238c3622a52e603dba94 (patch) | |
| tree | 7891ed854a34e57b98c2528943c08e104b3d83be /static | |
| parent | b1fe991fd3fb53a915c15f38896e4d1fd24e7bed (diff) | |
update info on porting
Diffstat (limited to 'static')
| -rw-r--r-- | static/build.html | 21 |
1 files changed, 12 insertions, 9 deletions
diff --git a/static/build.html b/static/build.html index 752d0df4..7c3a5ac9 100644 --- a/static/build.html +++ b/static/build.html @@ -176,15 +176,18 @@ <p><strong>We recommend using the sdk_phone64_x86_64 target in either the userdebug or eng variant for most development work.</strong></p> - <p>Providing proper support for a device or generic device family requires providing - an up-to-date kernel and device support code including driver libraries, firmware and - device SELinux policy extensions. Other than some special cases like the emulator, the - generic targets rely on the device support code present on the device. Shipping all of - this is necessary for full security updates and is tied to enabling verified boot / - attestation. Pixel targets have a lot of device-specific hardening in the AOSP base - along with some in GrapheneOS which needs to be ported over too. For example, various - security features in the kernel including type-based Control Flow Integrity (CFI) and - the shadow call stack are currently specific to the kernels for these devices.</p> + <p>Providing proper support for a device or generic device family requires + providing an up-to-date kernel and device support code including driver + libraries, firmware and device SELinux policy extensions. Other than some + special cases like the emulator, the generic targets rely on the device support + code present on the device. Shipping all of this is necessary for full security + updates and is tied to enabling verified boot / attestation. Device-specific + driver changes are required to support GrapheneOS features such as the + hardware-level USB-C port control. There's also a lot of device-specific work to + work around or resolve memory corruption bugs uncovered by our features. Most + devices are also missing a lot of standard hardware-based security features we + use such as hardware memory taggings so those features will inherently not be + possible to port to a device not capable of it.</p> </section> <section id="build-dependencies"> |