this post was submitted on 03 Oct 2024
209 points (97.7% liked)

DeGoogle Yourself

8837 readers
10 users here now

A community for those that would like to get away from Google.

Here you may post anything related to DeGoogling, why we should do it or good software alternatives!

Rules

  1. Be respectful even in disagreement

  2. No advertising unless it is very relevent and justified. Do not do this excessively.

  3. No low value posts / memes. We or you need to learn, or discuss something.

Related communities

!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml

founded 4 years ago
MODERATORS
CrypticCoffee@lemmy.ml
CrypticCoffee@lemm.ee
Byereddithellolemmy@lemmy.world
chevy9294@monero.town
209
Who owns your shiny new Pixel 9 phone? You can’t say no to Google’s surveillance (cybernews.com)
submitted 1 month ago by gytrash@feddit.uk to c/degoogle@lemmy.ml
116 comments fedilink hide all child comments
 

Google's latest flagship smartphone raises concerns about user privacy and security. It frequently transmits private user data to the tech giant before any app is installed. Moreover, the Cybernews research team has discovered that it potentially has remote management capabilities without user awareness or approval.

Cybernews researchers analyzed the new Pixel 9 Pro XL smartphone’s web traffic, focusing on what a new smartphone sends to Google.

“Every 15 minutes, Google Pixel 9 Pro XL sends a data packet to Google. The device shares location, email address, phone number, network status, and other telemetry. Even more concerning, the phone periodically attempts to download and run new code, potentially opening up security risks,” said Aras Nazarovas, a security researcher at Cybernews...

... “The amount of data transmitted and the potential for remote management casts doubt on who truly owns the device. Users may have paid for it, but the deep integration of surveillance systems in the ecosystem may leave users vulnerable to privacy violations,” Nazarovas said...

you are viewing a single comment's thread
view the rest of the comments
[–] Andromxda@lemmy.dbzer0.com 1 points 1 month ago

Err… That component appears to be built from source per Calyx’s Gradle rules? The source is pulled from here: https://android.googlesource.com/platform/frameworks/base/+/refs/heads/main/telephony/java/android/telephony/euicc

That's apparently not the entire thing though. I haven't used CalyxOS in a long time, could go to the settings menu for adding a new eSIM and take a screenshot of it?

I’m sorry you’re unhappy that I’m happy.

Oh I'm absolutely not. I'm glad you found an OS you like, I just pointed out that GrapheneOS is far superior in terms of privacy and security, and therefore probably the better choice, but you are obviously free to use whatever suits your needs and makes you happy. And it's better than the stock OS I guess.

My actual security relevant machinations happen on my much better protected laptop.

How do you protect a laptop to be more secure than a modern mobile device? Desktop operating systems are inherently less secure, since they lack proper application sandboxing, they often don't even have mandatory access control mechanisms (such as SELinux or AppArmor) in place and don't have a good way of verifying the boot image. Secure Boot is broken and essentially useless, and can't be compared to Android Verified Boot whatsoever. TPMs aren't secure either, and can't even remotely be compared with proper secure elements such as the Google Titan M2 or Apple's Secure Enclave. Do you use QubesOS, or how did you achieve better protection on your laptop compared to your smartphone?