> GrapheneOS is permissively licensed and is usable for building devices with an immutable root of trust. GPLv3 is deliberately incompatible with these kinds of locked down devices, unlike GPLv2 code such as the Linux kernel. This means GrapheneOS can't include GPLv3 code without forbidding use cases we want to support. GPLv3 is no problem for our own usage, but we don't want to forbid using GrapheneOS as a replacement for the Android Open Source Project in locked down devices.
They're not against GPLv3 and, but they explain why it's not suited for a project like GrapheneOS.
You can also use a privacy screen protector. Or use the two factor fingerprint unlock, which requires both a fingerprint and a PIN to unlock. And that's only after first unlock, so you can still use a separate, strong passphrase for BFU state.
Sure, a privacy screen makes things a bit more difficult for surveillance, because the camera would need a line of sight at a low angle, but once the code is known, the attacker can force a fingerprint and input the code.
And fully disable the USB port (GrapheneOS-exclusive feature). This will make it impossible to extract data with mobile forensics software/devices (such as the Cellebrite UFED).
GrapheneOS already has an auto-reboot feature that can be set to time intervals ranging from 10 minutes to 72 hours. Rebooting puts the device back in before first unlock (BFU) state. This wipes all memory contents, including the encryption keys. Any unlock attempt will have to go through the secure element, which is basically impossible to tamper with (no successful attacks on the Titan M2 so far, or the Apple SEP for that matter), and includes substantial security mechanisms, such as throttling key derivations (through the Weaver API), or insider attack resistance (requiring user authentication before new firmware can be flashed to the secure element).
It literally contains links to all the AOSP repos or GrapheneOS forks of them. You can clone these exact repos and build the OS from source. GrapheneOS provides instructions for it: https://grapheneos.org/build
Straight up conspiracy theories you're spreading here. Daniel Micay is Canadian, Dmytro Mukhomor is Ukrainian (he was literally conscripted into the Ukrainian army last year), and Khalykbek Yelshibekov is from Kazakhstan.
It's open source [1], and they're pretty transparent about everything. You can ask the devs anything, and they will probably give you a really useful and informative answer. They have extensive documentation, and they're pretty open, even about stuff like their servers [2], configurations [3], everything.
> GrapheneOS is permissively licensed and is usable for building devices with an immutable root of trust. GPLv3 is deliberately incompatible with these kinds of locked down devices, unlike GPLv2 code such as the Linux kernel. This means GrapheneOS can't include GPLv3 code without forbidding use cases we want to support. GPLv3 is no problem for our own usage, but we don't want to forbid using GrapheneOS as a replacement for the Android Open Source Project in locked down devices.
They're not against GPLv3 and, but they explain why it's not suited for a project like GrapheneOS.
[1] https://grapheneos.org/faq#:~:text=In%20some%20cases,locked%...