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

fix typos, reword some phrases, and add extra info

Browse Source 
Also, mention IP68 water and dust resistance for Pixel 3/3 XL
This commit is contained in:
inthewaves 2020-02-18 22:41:42 +00:00 committed by Daniel Micay
parent c2eaa511dc
commit eaa01c67ae
1 changed files with 15 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
static/faq.html
View File

@ -119,12 +119,13 @@
along with the longest future support time are the Pixel 3a, Pixel 3a XL, Pixel 3 and
Pixel 3 XL. The Pixel 3a and 3a XL are budget devices meeting the same security
standards as the more expensive flagship devices. Compared to the Pixel 3a and 3a XL,
the flagshig Pixel 3 and Pixel 3 XL have wireless charging, dual front-facing
speakers, the Pixel Visual Core supporting HDR+ with compatible apps on GrapheneOS, a
higher-end screen, slightly more durable glass and of course a stronger CPU, GPU,
cellular radio, etc. You should get one of the budget devices if these things aren't
compelling to you. The Pixel 3a and 3a XL do have one extra feature: an analog
headphone port as an alternative to wireless audio and digital USB-C audio.</p>
the flagship Pixel 3 and Pixel 3 XL have wireless charging, dual front-facing speakers,
the Pixel Visual Core supporting HDR+ with compatible apps on GrapheneOS, IP68 dust
and water protection, a higher-end screen, slightly more durable glass and of course a
stronger CPU, GPU, cellular radio, etc. You should get one of the budget devices if
these things aren't compelling to you. The Pixel 3a and 3a XL do have one extra
feature: an analog headphone port as an alternative to wireless audio and digital
USB-C audio.</p>
<h2 id="future-devices">
<a href="#future-devices">Which devices will be supported in the future?</a>
@ -138,18 +139,18 @@
devices, and officially supported devices are the ones targeted by most of this
ongoing work.</p>
<p>Devices need to be meet the standards of the project in order to be considered as
<p>Devices need to be meeting the standards of the project in order to be considered as
potential targets. In addition to support for installing other operating systems,
standard hardware-based security features like the hardware-backed keystores, verified
boot, attestation and various hardware-based exploit mitigations need to be available.
Devices also need to have decent integration of IOMMUs for isolating components such
as the GPU, radios (NFC, Wi-Fi, Bluetooth, Cellular), media decode / encode, image
processor, etc. as if the hardware / firmware support is missing or broken, there's
not much that the OS can do to provide an alternative. Devices with support for
processor, etc., because if the hardware / firmware support is missing or broken,
there's not much that the OS can do to provide an alternative. Devices with support for
alternative operating systems as an afterthought will not be considered. Devices need
to have proper ongoing support for their firmware and software specific to the
hardware like drivers in order to provide proper full security updates too. Devices
that are end-of-life and no longer receiving these updates will not be supported.</p>
to have proper ongoing support for their firmware and software specific to the hardware
like drivers in order to provide proper full security updates too. Devices that are
end-of-life and no longer receiving these updates will not be supported.</p>
<p>In order to support a device, the appropriate resources also need to be available
and dedicated towards it. Releases for each supported device need to be robust and
@ -175,8 +176,8 @@
are uncovered, which will include issues uncovered in the device support code by
GrapheneOS hardening features.</p>
<p>It's not really a matter of time but rather depends on community support for the
project increasing. As an open source project, the way the get something to happen in
<p>It's not really a matter of time but rather a need for community support for the
project increasing. As an open source project, the way to get something to happen in
GrapheneOS is to contribute to it, and this is particularly true for device support
since it's very self-contained and can be delegated to separate teams for each
device. If you want to see more devices supported sooner, you should get to work on