Nostr notes by skorp

@npub1s64…vnps I don't know about that, but it depends how ...

2025-09-22T21:03:10+02:00

In reply to nevent1q…cn3c
_________________________

Linux__ (npub1s64…vnps)

I don't know about that, but it depends how you define "safe enough". If you mean to defend against any relatively recent types of remote or local exploits, then no.

Installing a mobile Linux distro adapted from desktop doesn't fix the horribly outdated firmware. That is why GrapheneOS does not provide support past this point. Without proper firmware *and* OS support, the devices quickly become vulnerable and someone other than the OEM providing firmware patches is infeasible to the point of near impossibility.

This isn't even touching on the general and egregious lack of security on desktop and desktop-based platforms either.

But yes, I suppose it is dependent on your threat model and priorities. If we want options other than Pixels and iPhones as secure devices then we should pressure other OEMs to meet a higher bar.

There is no indication that Google will be locking the bootloader ...

2025-09-22T20:19:23+02:00

In reply to nevent1q…dlwc
_________________________

There is no indication that Google will be locking the bootloader on Pixel devices.

GrapheneOS is also working with an OEM to add more supported devices in the next couple years.

Fairphones are highly insecure devices and /e/OS is also highly insecure and non-private.

Oh no! No apology necessary or expected.

2025-08-29T21:30:14+02:00

In reply to nevent1q…ges8
_________________________

Oh no! No apology necessary or expected.

No worries! Only here to provide clarity :)

2025-08-29T21:21:13+02:00

In reply to nevent1q…ltts
_________________________

No worries! Only here to provide clarity :)

Rooting is actually not part of the process of installing ...

2025-08-29T21:12:35+02:00

In reply to nevent1q…yhud
_________________________

Rooting is actually not part of the process of installing GrapheneOS (if that was your intention). Root access is antithetical to the goals of GrapheneOS and is not supported by the project or the community.

Hi! Just a note about root in general and some about how it ...

2025-08-29T04:23:24+02:00

In reply to nevent1q…8vz5
_________________________

Hi!

Just a note about root in general and some about how it relates to GrapheneOS.

Root is, generally speaking, something that is highly insecure to have available to the user on any system. On something like Android, where you expose root access via user accessible UI, it _completely_ undermines the Android security model. It allows runtime modification of the OS which means that any app or service that bypasses the trivial UI prompt can now escalate itself to root privilege. I.e. you cannot partially grant godhood.

GrapheneOS makes many many security and privacy improvements that would be undermined at a fundamental level if you were to root it. And by their definition, it becomes no longer GrapheneOS but a fork you have created and is on you to maintain.

You mentioned liking to have control over your device. Think about control as the ability to be sure that when you grant or deny a permission or access to apps, etc on your device, it is guaranteed that those apps follow the rules you set. If you root, you lose that guarantee and that control.