- cross-posted to:
- protonprivacy@lemmy.world
- cross-posted to:
- protonprivacy@lemmy.world
No answer yet from what I’ve seen. Possibly Mess up from an unreviewed vibe coded mess. Or worse yet , intentional.
No answer yet from what I’ve seen. Possibly Mess up from an unreviewed vibe coded mess. Or worse yet , intentional.
https://developers.google.com/ml-kit
https://developers.google.com/ml-kit/vision/doc-scanner
It’s on-device scanning and OCR and stuff. I fail to see how this is a privacy concern? Your documents aren’t leaving your device and they’re not being uploaded to Google servers. This really seems like a false moral outrage imo. Y’all really wanna hate Proton because the CEO is a dickbag but c’mon man, this doesn’t scream vibe coded, low quality, or insecure/non-private to me. I’m guessing this is just to allow you to upload documents to Proton using your phone as a scanner.
Concerning
https://www.privacyaffairs.com/proton-drive-google-ml-kit/
ML Kit isn’t silent, though. Google’s data disclosure for ML Kit lists what its Android libraries collect for diagnostics and usage analytics:
Device: maker, model, OS version and available ML hardware.
App: package name and version.
Identifiers: a device identifier for features delivered through Play services, like this scanner, plus per-installation identifiers.
Usage: performance figures, settings, input and output sizes, events such as start-ups, model downloads and detections, and error codes.
Kudos for actually looking into this at all and not just having feelings on the subject.
Having said that, that usage data is not sold or made available for non-development purposes: https://developers.google.com/ml-kit/android-data-disclosure
Overview of data encryption and data sharing for ML Kit Android SDKs:
I also haven’t proven this out, but I think the devs should be able to block that behavior in the apps manifest and prevent the telemetry uploader from running.
Thank you for the additional context!
Proton has issues as a company but it feels like 50% of the negative headlines or coverage they get ends up not being an accurate representation.
The other 50% sucks tho, which is a bummer
It really is. A spotty record like this is simply not good enough for a company putting forth privacy and security as its chief features and product differentiators. You’re either all in on those things or you’re not.
Is there a guarantee ML kit stays on device or we just taking Googles word for it ?
It would be pretty easy to demonstrate the opposite, a security researcher could do it in a jiffy, so it wouldn’t make sense for Google to lie about it.
Yes, but also no, never know what G will do next, once you include their libraries terms can change on a whim.
ETA: Apparently terms already permit exfiltration of identifiers and ‘performance figures, settings, input and output sizes, events such as start-ups, model downloads and detections, and error codes.’ (thanks BrilliantBadger) So simple detection won’t work.
You can sniff packets heading out of the device if you’re so invested. Proton should frankly be the ones testing and making that statement clear, but you can too.
MLK phones home, so it’s more a matter of taking Google’s word that they’re not sending your data back.
A phone home ping looks very different from uploading scanned files, even if the messages are encrypted.
It’s literally OCR, how can you tell they’re not sending the text?
Any code from google is either a problem or a future problem. And before you say “what about x?” my answer will be “nope”.
It’s not against proton… But can you trust anything that is “on device” from G?
Go offline, scan, encrypt, zip with password, purge the original file somehow then go online… Even then you can’t be sure there ia not some thumbnail, copy, screenshot being made and send to G
It’s trivially easy to prove it works offline, and it would be also very easy to sniff traffic on device or MITM yourself to verify traffic isn’t flowing to Google.
As a closed-source package it’s not possible to inspect the source but it would be very easy to catch them in the act, even with it as a black box.
MLK phones home, so it’s more a matter of taking Google’s word that they’re not sending your data back.
Not really, you can tcpdump it or MITM yourself and read the data that’s being sent.
The app devs can also block the telemetry uploaded from running, which should be inspectacle from apps manifest.
Not an expert, but can you if it’s encrypted?
Yeah but are they? Especially considering the recent turns proton has taken.
Yeah you have to get the TLS cert so it’s annoying but you can definitely decrypt HTTPS traffic via tcpdump. It might be extra annoying over Android but it’s definitely possible somehow.
Worst case you fake the cert and MITM your device and sniff as you pass it upstream. It’s a lot of work but…
I don’t get it. The whole point of encryption is that only the recipient can decrypt it, regardless of what role you play in the middle. Unless you’re reading it before the encryption happens.
Not saying it’s bullshit, just not jiving with my very basic understanding of this.
For MITM attacks you need to own the network you’re on and then you have the client connect to you with a cert the client will trust (by adding to the client’s trusted cert bundles or or or) and then sniff as you proxy upstream to the real intended host.
This is why people say not to trust random WiFi networks.
For option 1, since you are the device, you just need to use the TLS certificate from the session, which you can capture otherwise. This is just the first source I could find: https://support.atlassian.com/atlassian-knowledge-base/kb/how-to-capture-http-traffic-using-wireshark-fiddler-or-tcpdump/
What means “on device”?
Like pornography “on device scanner” that is automatically installed and enabled on Android and Apple devices…
Yes it works on device like everything else but once it detects something illegal on device then it flags you to the server…
Uploading and then scanning pictures at Google pictures wasn’t enough so now scanner is also “on device” and “for your safety” and to warn you before you send nudes or look at received ones.
This isn’t at all an implementation of OCR for the purposes of using a phone as a scanner. This is putting the foundations in to allow AI to utilize the contents of your e-mails.
That’s a huge privacy nightmare…
Ideally the only people reading e-mails should be the senders and the recipients. Instead you also have this thing–doesn’t matter if it’s offline or online. It’s a piece of software trying to contextualize private communications.
Apparently they are improving the on device search, so I assume it’s for OCRing attachments for content search