-
-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ADDITION] /e/OS (Complete) #256
Comments
If you're enjoying Awesome-Privacy, consider dropping us a ⭐ |
This description is some first class marketing bullshit imho.
If no one does the auditing, it's an empty claim.
"privacy-enabled"? "internal system"? Those are some made up terms for ya. Pure marketing, no substance.
Logical fallacy. https://en.wikipedia.org/wiki/Argument_from_authority /e/OS is nothing more than a regularly outdated LineageOS, a Nextcloud server and some (rebranded and, again, regularly outdated) apps. I mention outdated twice, since because of this you're running software - for months at a time - with known 0-days that have already been fixed for others. See for instance https://divestos.eeyo.re/misc/ch-dates.txt |
Im so sorry for my copied description. I found a paper linked to the website of this program,heres it : https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf There is a simple detail : I found "- /e/OS 123.0.6312.122, downstream Cromite https://gitlab.e.foundation/e/os/browser/-/commits/master" appears on the given link https://divestos.eeyo.re/misc/ch-dates.txt , thus I also suggest considering adding iodéOS to our list : "- iodéOS tracks LineageOS/master https://gitlab.com/iode/os/public/manifests/android/-/blob/v4-staging/snippets/lineage.xml" |
While it might be possible that /e/OS has applied some patches to minimize communication with Google servers compared to LineageOS, the only difference with between them in that paper is that the researchers just installed the Google ecosystem (opengapps) on top of LineageOS, which isn't the default. No wonder LineageOS sends data to Google in that case. What can be found in that text file is that the /e/OS browser (indeed a rebranded Cromite) is updated very irregularly, often with gaps of multiple months. I would recommend using Cromite instead. However, this does not update the WebView renderer, often used inside other apps, so you'll still be vulnerable (assuming they use the Cromite WebView: it'll be less outdated, but also less privacy-friendly, if they just use LineageOS's own WebView and indeed provide monthly OTA updates). I have no info about iodéOS. |
Thanks again for your patient review. I cant resolve those essential privacy problem youve mentioned,but there are features about /e/OS I can see: About iodéOS , see https://iode.tech/iodeos-en/ and I think it also belongs to the family of Lineage (Just in the meaning of privacy focusing). They also offer pre-installed fairphone in their shop. That my simple suggestion above,if these cant help construct our project and Ill close this issue. |
Well, the problems I mentioned are security problems, not privacy problems, but yeah, apart from that there's a lot to say for /e/OS's approach of providing people with a more complete alternative to the Google ecosystem. Disclaimer: these are just my 2 cents, I'm not in the position to officially review anything here 🙂 |
Category
Operating Systems
Listing Name
/e/OS
Listing URL
https://e.foundation/get-started/
Listing Icon
https://e.foundation/wp-content/uploads/2022/11/e-logo-noir-01.png
Listing Description
/e/OS is an open-source mobile operating system paired with carefully selected applications. They form a privacy-enabled internal system for your smartphone. And it’s not just claims: open-source means auditable privacy. /e/OS has received academic recognition from researchers at the University of Edinburgh and Trinity College of Dublin.
GitHub repository
https://gitlab.e.foundation/e
ToS;DR ID
No response
Is Open Source?
Security Audited?
Accepts Anon Payment?
Justification and Further Info
YAML Content for Addition
This ticket was submitted via awesome-privacy.xyz/submit
Final Checklist
The text was updated successfully, but these errors were encountered: