4 ms·
Are you on Android? Use Firefox with NoScript or uMatrix (also as your default webview) and setup AdGuard DNS [0] or a pi-hole. You could consider using a VPN l
by ignoramous 8y ago
Are you on Android? Use Firefox with NoScript or uMatrix (also as your default webview) and setup AdGuard DNS [0] or a pi-hole. You could consider using a VPN like Orbot (free Tor-as-a-proxy) [1], PerfectPrivacyVPN (supports multiple exit IPs, multiple-hops, and server side firewall) or set one up using Algo/Streisand [2].
If you do not want to root your device:
1. Install NetGuard or No Root Firewall to view what's going on from network perspective.
2. Install ExodusPrivacy to generate a report on apps wrt sdks in use by them.
---
If you are okay to root the device:
1. Install XposedMod, and then XPrivacyLua module, and work through the options.
---
If you're okay with flashing a ROM:
1. Consider LineageOS + microG
2. If you are using Pixel, consider ChromeheadOS (edit: CopperheadOS) [3].
---
If you're okay with a new device:
1. Consider purchasing puri.sm Librem 5.
---
[0] https://news.ycombinator.com/item?id=18788410 https://news.ycombinator.com/item?id=18788410
[1] https://guardianproject.info/apps/orbot/ https://guardianproject.info/apps/orbot/
[2] https://github.com/trailofbits/algo https://github.com/trailofbits/algo
[3] https://copperhead.co/android/ https://copperhead.co/android/
- mindslight 8y agoIf you're worried about flashing your device, go spend $100 on a device off the LineageOS list of supported devices, and experiment with that instead. The odds are it'll go fine and you'll be happily using it three months from now.
- kzcqt 8y agoI think in 2019 it's practically impossible to completely brick a mobile by flashing wrong stuff on it.
- ignoramous 8y agoTrue, not because it's 2019 but due to Project Treble's GenericSystemImages that cleanly separate OEM (Samsung, Sony, Lenovo) and silicon-vendor (Broadcom, Qualcomm, Mediatek) related blobs from the Android subsystem, such that the Android bits could be changed or updated independent of vendor support. https://android-developers.googleblog.com/2018/11/an-update-on-project-treble.html?m=1 https://android-developers.googleblog.com/2018/11/an-update-...
- johnnycab 8y agoEven a cursory glance at some of the sections on XDA or a search for '2019' and 'brick a mobile' will reveal that they are not mutually exclusive events.
- kzcqt 8y agoI meant to completely brick a mobile. As a newbie, it's possible to get into a boot loop, a black screen, etc. which are easy to recover events, but might seem as the end of the world. I even remember having to short two pins in the motherboard of my mobile to recover from a particularly bad brick. And it worked fine. But a complete brick, as in you have to throw away your mobile? Impossible, I'd say.
- colejohnson66 8y agoThat’s kind of splitting hairs, isn’t it?
- mindslight 8y agoSure, but that won't help convince someone who's justifiably worried about putting their primary device out of commission.
- minton 8y agoFor those curious you can find that list here: https://wiki.lineageos.org/devices https://wiki.lineageos.org/devices
- prophesi 8y agoDo you have a link to ChromeheadOS? I somehow can't find it via startpage or google.
- ignoramous 8y agoMy bad. Sorry, it's CopperheadOS https://copperhead.co/android/ https://copperhead.co/android/
- prophesi 8y agoahh, thanks! I should've known that.
- nextos 8y agoI would be a bit reluctant to run CopperheadOS now. Sadly the main developer left after somewhat hostile actions from the CEO, and there have been lots of changes in the organization. IMHO the best option for a secure phone is pure Android without Google blobs. That is, AOSP on a Pixel phone. Plus an F-Droid userland. If a Pixel is too expensive, you can always try to get an AOSP device-independent image on a new phone that supports Treble. For example, the super cheap Nokia 1 seems to work well [1]. [1] https://github.com/phhusson/treble_experimentations/wiki https://github.com/phhusson/treble_experimentations/wiki
- ignoramous 8y agoAOSP is clean, but doesn't have anti tracking measures available in CopperheadOS: fake IMEI or MAC addresses (this has been mainlined in Android Q, though), for instance.
- danvittegleo 8y agoAgreed. For anyone interested in doing their own monthly signed AOSP builds for Pixel phones with OTA updates, take a look at a project that I built that fully automates the process in AWS: https://github.com/dan-v/rattlesnakeos-stack https://github.com/dan-v/rattlesnakeos-stack.
- 8y ago
- Skunkleton 8y agoFor anyone considering the above, this is a failing battle. The only way to stop this sort of tracking is if we have a cultural shift, start putting laws in place, and actually enforce them. For example, did you know that many shopping malls track you with license plate readers? Did you know that your credit card transactions are up for sale? Or that your cell phone provider will give up your location to a third party with a flimsy consent?
- ignoramous 8y agoYou are absolutely right that we need laws and regulations to govern all the tracking that's going on, much like how call-tapping is illegal. Bruce Schneier has written a book on the topic, and you can view him speak on it here: https://youtube.com/watch?v=GkJCI3_jbtg https://youtube.com/watch?v=GkJCI3_jbtg Highly recommend it. I'm no expert but I do not agree with the 'failing battle' part... still quite a way to go in that regard, I think, specifically because the Math behind crypto hasn't failed us yet (ocassionally, the implementation has) and because the government agencies themselves need tech that helps them stay underground (Tor, for instance, continues to get funding from the US Government). Is it getting difficult? Yes, absolutely. People still hold the 'nothing to hide' stance and most are okay giving up privacy esp if it means their life becomes a little more secure and things get more convenient (most would support AI powered street surveillance that helps keep tabs on criminals, for instance).
- DavideNL 8y agoIn the end unfortunately none of the ad/tracker blocking solutions are solid; All an app developer has to do is use an IP address to fetch ads (avoiding dns resolution and thus dns based blocking won't work.) Or, fetching the ads from the same hostname as also used by the app itself to provide whichever service the app provides, which means that hostname can't be blocked even by a firewall because the app itself will stop working. So i agree, the only proper solution is laws to stop the privacy abuse.
- crankylinuxuser 8y ago
- OrgNet 8y ago> If you do not want to root your device: I want to but I can't even if I "own" it. > 1. Consider LineageOS + microG Probably should avoid microG if you care about privacy...