e/OS vs. AOSP: Users Fear Vendor Backdoors as Data Giants Persist
The debate centers on securing Fairphone 5 hardware against pervasive data collection, contrasting minimal OS offerings with established open-source builds. A significant, immediate concern involves the security patch status of e/OS compared to up-to-date AOSP builds, a risk flagged specifically by 'abr'.
Commenters openly acknowledge that perfect privacy is technically impossible. 'Atemu' warns that even with Google's own minimal implementations like µG, using any third-party app relying on Google services still leaks data. Similarly, 'jjlinux' dismisses the idea of foolproof pseudonymity, warning that large data aggregators can still link pseudonymous profiles to real identities.
The consensus points toward intense, layered technical mitigation. Achieving privacy requires combining local controls like Pihole/Adguard home with advanced networking gear like PFSense firewalls, acknowledging that simple DNS blocking is inadequate on its own.
Key Points
Achieving 100% privacy is an operational myth requiring complex, layered defense.
Multiple users agree complex tech stacks (PFSense, VPN chaining, local DNS) are the minimum baseline, dismissing simple fixes.
Vendor-specific OS layers (e/OS) carry unquantified security risks.
'abr' flagged specific concern that e/OS might lag on crucial security patches compared to modern AOSP builds.
Google services inherently compromise privacy, even when minimized.
'Atemu' stated that minimal Google implementations fail when third-party apps integrate Google analytics or services.
Pseudonymous online identities are structurally susceptible to linkage attacks.
'jjlinux' asserted that large data aggregators possess the capability to de-anonymize even carefully constructed profiles.
Advanced network security demands multi-point VPN chaining and dedicated firewall hardware.
'jjlinux' provided a detailed, high-bar example involving PFSense, Starlink/fiber load balancing, and multiple VPN providers.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.