this post was submitted on 20 Jul 2024
94 points (96.1% liked)

Privacy

31975 readers
646 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

Im considering buying a new phone and i don't really consider a Pixel. I really like Fairphones approach, with the self repairable stuff. Even though they don‘t have a headphone jack. But well… I can’t change it. I’ll definitely go with the adapter over wireless headphones.

But to my question: What private OSes are there? Fairphone sells FP4s with eOS, how is that? And does it work on the FP5? GrapheneOS only works on Google Pixels right?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 30 points 3 months ago (6 children)

In that case, have fun coding up your own bootloader and flashing it onto the device. If you can't trust the bootloader, then you can't trust anything at all from the operating system that sits on top of it, because it could be compromised. If you can't trust a bootloader, then the only thing you can trust is a pen and a piece of paper.

[–] [email protected] 1 points 3 months ago (3 children)

why dont we just put uefi on phones

[–] [email protected] 1 points 3 months ago (2 children)

Phones don't use an IBM-PC architecture. You'd need a phone based on an architecture phones aren't usually based on or You'd need to re-engineer UEFI to work for an architecture it wasn't designed for

[–] [email protected] 3 points 3 months ago (1 children)

UEFI has supported ARM for years now...

[–] [email protected] 1 points 3 months ago

And "phones don't use UEFI"

load more comments (2 replies)