No answer yet from what I’ve seen. Possibly Mess up from an unreviewed vibe coded mess. Or worse yet , intentional.

you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 1 day ago (12 children)

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.

  • source
  • parent
  • hideshow 12 child comments
  • [–] 3 points 19 hours ago (11 children)

    MLK phones home, so it's more a matter of taking Google's word that they're not sending your data back.

  • source
  • parent
  • hideshow 11 child comments
  • [–] 1 point 18 hours ago (10 children)

    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.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 0 points 18 hours ago (9 children)

    Not an expert, but can you if it's encrypted?

    The app devs can also block the telemetry uploaded from running

    Yeah but are they? Especially considering the recent turns proton has taken.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 2 points 18 hours ago (8 children)

    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...

  • source
  • parent
  • hideshow 8 child comments
  • [–] 1 point 11 hours ago (3 children)

    You arent getting google's private cert. You can decrypt data they send. Not the other way around. HTTPS encryption is asymmetric. You cannot decrypt data you yourself encrypt that easily. Their TLS cert provides the encryption, not decryption.

    That being said, blocking the HTTPS data collection endpoint is a lot more trivial to do.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 8 hours ago* (2 children)

    You don't need Google's private cert to decrypt HTTPS traffic, you just need the keys from the TLS handshake your client performs. As you are the client, you can sniff your own traffic. I've personally done this using wireshark. I've already provided one link from a trustworthy source, feel free to search for more if you choose.

    https://support.atlassian.com/atlassian-knowledge-base/kb/how-to-capture-http-traffic-using-wireshark-fiddler-or-tcpdump/

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 hours ago (1 child)

    Does this not state you need the actual clienr application to be involved in the process? Where are you getting the session key here? Its not a browser.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 hours ago

    You just need access to the client itself, which in this case if you cared enough to go this far, could be a sample app that you're just using to test MLKit's behavior. Custom app means you can do whatever you want as part of the TLS handshake, including dumping the negotiated keys to a logfile. Again, it would be non-trivial work, but it's absolutely possible. If anyone was sufficiently motivated, they could do it.

  • source
  • parent
  • [–] 1 point 18 hours ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 18 hours ago* (last edited 18 hours ago)

    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.

  • source
  • parent
  • [–] 2 points 18 hours ago (1 child)

    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/

    Decrypt with SSLKEYLOGFILE

    Wireshark has the ability to use SSLKEYLOGFILE to decrypt https traffic. This file is a feature provided by the web browser. When a Web Browser is configured to create and use this file all of the encryption keys created for that session are logged. This allows Wireshark to decrypt the traffic. If you supply SSLKEYLOGFILE and a pcap file that were taken at the same time, wireshark will show you all of the web traffic.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)