Remix clone Hacker News

new | show | ask | jobs Github

▲

zb3 8 hours ago

If GrapheneOS won't plan on supporting that it means it's not as secure as advertised.

▲

NooneAtAll3 7 hours ago | parent | next [-]

GrapheneOS devs state requirements based on Pixels, not choose Pixels based on requirements

so I won't trust judgement based on that

	▲	anonym29 2 hours ago \| parent \| next [-]
		GrapheneOS publishes a list of the requirements: https://grapheneos.org/faq#future-devices GrapheneOS devs have announced "We're currently working with a major OEM towards future generations of their devices meeting our requirements and providing official GrapheneOS support. GrapheneOS on both Pixels and these future non-Pixels will be fine." (https://grapheneos.social/@GrapheneOS/115102564799343519) You're welcome to assert otherwise, of course, but your assertions are contradictory with direct statements from the GrapheneOS team.
	▲	lawn 6 hours ago \| parent \| prev [-]
		Not at all and ignorant of you to think so.

▲

joemazerino 8 hours ago | parent | prev [-]

No, it means the phone isn't suitable for security maximalists. GrapheneOS doesn't support any hardware except the Pixels.

▲

Bender 8 hours ago | parent [-]

And that's even assuming one cares about the secure enclave. I am not convinced that any phones exist that one can not unlock the enclave via JTAG debugging.

	▲	SoftTalker 7 hours ago \| parent [-]
		For most devices, if you have that kind of physical access, and enough technical resources, all bets are off. Most people's threat model doesn't include three-letter-agencies reading their secure enclave. If yours does, you're probably better off not carrying a phone at all.