diff options
Diffstat (limited to 'content/entry/the-problem-with-grapheneos.md')
| -rw-r--r-- | content/entry/the-problem-with-grapheneos.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/entry/the-problem-with-grapheneos.md b/content/entry/the-problem-with-grapheneos.md index fc96c20..cbea307 100644 --- a/content/entry/the-problem-with-grapheneos.md +++ b/content/entry/the-problem-with-grapheneos.md @@ -20,7 +20,7 @@ Yes it's a problem for all custom Android roms, but I'm picking on GrapheneOS in In my opinion, calling your operating system (OS) "private and secure" while not acknowledging the risk of the proprietary blobs required to run it is misleading. It's one thing if your OS can also run on open hardware or the proprietary firmware it requires is very limited, but it's another thing entirely when your OS only runs on very closed hardware. Free software, privacy, and security go hand in hand. You can't just ignore hundreds of megabytes of unauditable proprietary blobs that run at boot time and still pretend it's a secure device just because you have hardened malloc. -Also, there's another problem with the proprietary firmware which GrapheneOS doesn't sufficiently address in my opinion. Since GrapheneOS requires up-to-date proprietary firmware to support devices, it's entirely dependent on [OEMs](https://www.wikipedia.org/wiki/Original_equipment_manufacturer "Original Equipment Manufacturer") to update that firmware. But it's in the OEM's economic self-interest to stop providing support as soon as they're not legally obligated to. +Also, there's another problem with the proprietary firmware which GrapheneOS doesn't sufficiently address in my opinion. Since GrapheneOS requires up-to-date proprietary firmware to support devices, it's entirely dependent on [OEMs](https://en.wikipedia.org/wiki/Original_equipment_manufacturer "Original Equipment Manufacturer") to update that firmware. But it's in the OEM's economic self-interest to stop providing support as soon as they're not legally obligated to. Why is this GrapheneOS' problem? Well if privacy-conscious people are promoting GrapheneOS, some might purchase new Pixel phones to keep up with GrapheneOS' releases. This funnels more money into proprietary hardware, perpetuating the cycle of endless e-waste rather than funding open hardware, which is less wasteful and clearly the right direction for privacy and security. GrapheneOS could warn people against buying new Pixel phones just to install their OS and instead suggest supporting open hardware. |