Google’s motives, part 2

Now I think I finally get why Google wants HTTPS everywhere.

  1. A lot of pages have Google code embedded in them.
  2. This code sends data back to Google.
  3. Suppose Comcast wanted to track users in addition to Google, or in place of Google.
  4. Now as the text of my page passes through their router, they simply modify the Google code, and leave the rest of the page alone.
  5. They wouldn’t want to alert anyone to what they’re doing, so they’d keep it as innocuous as possible. They probably would leave the Google code in, at least at first, so as to not arouse suspicion.
  6. They can do this because a lot of the sites that include Google code don’t use HTTPS.
  7. This assumes Comcast can’t crack the HTTPS. I have no info either way on that.

Disclaimer: I never wanted to have to understand this stuff.

More: They probably couldn’t care less about pages that have no code in them.

Also: Of course it’s not just Comcast. All the mobile providers. In Europe, Asia, everywhere. And it’s Facebook too. They have a browser coming too.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.