←back to thread

286 points joegibbs | 2 comments | | HN request time: 0.419s | source
Show context
noident ◴[] No.42143494[source]
This "novel" feature is already supported by GrapheneOS and set to trigger after 18 hours by default, with the option for the user to adjust it to their preference. There is no good reason to force the choice of 72 hours on everybody. That's a user-hostile design decision.
replies(7): >>42143499 #>>42143613 #>>42143615 #>>42143626 #>>42143707 #>>42143726 #>>42143864 #
summermusic ◴[] No.42143864[source]
This is an essential feature for my personal GrapheneOS phone. I only tend to use it once or twice a day most days, which means it is usually freshly rebooted every time I go to use it.

I remember reading somewhere that many new exploits in the mobile space only exist in memory and are thwarted by a simple reboot, including the infamous Pegasus spyware.

replies(2): >>42144722 #>>42145477 #
ruthmarx ◴[] No.42144722[source]
Graphene might be great, but the Google specific hardware that is the only thing it will run on might not be as trustworthy.
replies(1): >>42145243 #
1. bohdanqq ◴[] No.42145243[source]
Graphene is not limited to Google hardware, it's just that Google hardware meets their hardware requirements... (https://grapheneos.org/faq#future-devices).

AFAIK (from observing GOS comm channels) verified boot (alternative OSes but even the mechanism itself since some OEMs customize quite a bit), hardware rate limiting and timely security patches (which include modem firmware, preloaders - i.e. hardware) are the main reasons other devices are not supported.

replies(1): >>42145359 #
2. Malidir ◴[] No.42145359[source]
It is limited at moment to just pixel!