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
[–] 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 7 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