Privacy
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 :)
It’s a very valid question in my opinion and as is often the case with security, it really depends on your individual threat model and threat tolerance. As you said it seems pretty unlikely that a maintainer would install malicious code as they have a reputation to protect. And as mentioned by another commenter, even if you compiled the code yourself, unless you can audit code yourself you still have to just trust the developers. Personally for my threat tolerance, I do not see the risk as big enough to warrant the extra effort.
Auditing the code may seem as a problem but such a big project is already been auditing by many developers worldwide which means it is highly unlikely they all are sus
We are talking about maintainer's backdoor in build, not in original code 🙂
even if you compiled the code yourself, unless you can audit code yourself you still have to just trust the developers
That is what I was referring to. What I was saying is even if you cant audit the source code you still have reasons to trust the code
Yeah, I have many reasons to trust the code. Definetly. If it is in build and nothing else then we are good!
Agreed, too much hussle and money to rent powerful server.
You don't need a powerful server to build LineageOS. 16 GB of RAM and some patience was enough when I last did it.
hmm, good news. but REALLY much disk space available, 300gb ~ 😁
wow. yeah, i remember trying to build lineage for my old phone after support ended and the people on xdadevelopers also stopped making inofficial builds. my notebook wasn't up to the task. not enough ram, too much data on the ssd.
My LineageOS 17 (Android 10) build tree is under 200GB. Adding a ccache dir puts it just slightly over that.
Used hard drives twice that size are cheap.
👍
If you decided to use ROM, at least do it the right way. Build it, what will you lose? Couple hours you cant touch your computer? Go touch grass
Fair point.
Trust is something only you can give.
I tend to trust known developers that work on projects without scandals in the last 5 years.
Good approach!
If you have the free time and the technical expertise, go for it!
💯
Don't do it for security reasons. Do it because you can😎
this!