this post was submitted on 26 Oct 2023
32 points (92.1% liked)
Privacy
31837 readers
80 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
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The only secure phone operating systems are either grapheneOS or stock. All the others usually are behind security updates.
For migration, I would just use a USB C drive and transfer files.
Uhm, not necessarily. First of all, aosp should get security updates at the same time as graphene (or earlier, which is more likely); then there are non-pixel phones (yuck, I know) that aren't supported by graphene guys, and when those go eol, custom roms often keep pushing [software] security updates for some time at least (source: this message is sent from a 1+5t running DivestOS based on android 13); finally, stock roms may arguably ('cause vendors introduce bloatware, which can potentially be used in ways not intended by its developers) be more secure, but they suck at privacy department in like 99 of 100 cases
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.
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.