Privacy

32173 readers

719 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

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

[email protected]

Switching to custom rom on android device with data (infosec.pub)

submitted 1 year ago by [email protected] to c/[email protected]

25 comments fedilink hide all child comments

Hello all,

Currently I am debating whether or not to switch to a (preferably private/secure) custom rom on my device, however said device had been in use for a while now.

My question is the following: For those who have been in this situation, how have you dealt with the existing data on the device in terms of migration? After all, switching ROM usually involves a factory reset. Creating backups of everything is a bit tedious and timeconsuming and there is always the possibility of forgetting something.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

AOSP does get security updates first because GrapheneOS is based on unmodified AOSP. They are quick to port over updates though and they have extra features like hardened malloc and better user profile support.

Non pixel phones aren't secure because GrapheneOS doesn't support them. They aren't secure because they either don't have secure elements, broken verified boot, or don't properly support alternative operating systems. This makes phones like OnePlus, Fairphone, etc not secure enough for GrapheneOS.

DivestOS I would say is the least worst option when it comes to supporting EoL phones. They're at least honest about what they do and don't provide unlike what other OSes do. On their website, they tell you they aren't a secure OS and they can only try their best to reduce harm on an EoL device. DivestOS Security.

[–] [email protected] 2 points 1 year ago

Pretty much agreed. Although, onepluses used to be quite good before they decided to stop allowing setting custom vb keys.

What I wanted to say is that security is a spectrum, and stock roms aren't necessarily the best.

P.s. other roms sometimes use stuff like hardened malloc as well (ik that its developed by graphene, tho) yet none (except graphene itself, ofc) I've personally tested have storage (and as of recently cobtact) scopes which is quite sad.