Hacker GitHub

← All repos

GoogleChrome/ip-protection

View on GitHub ↗ ★ 392 archived

12 mentions on Hacker News by 12 people: 2 stories, 10 comments · first 2023-10-23 · latest 2025-02-17

Mentions per year 12 mentions · busiest year 2023 (5)
20082026
  1. …for the very limited information that we do have, let me confirm things internally and circle back. https://github.com/GoogleChrome/ip-protection/issues/34 Disclosure: I work at Google, but not on IP protection.
  2. …for incognito users. I believe Chrome originally planned to roll out IP protection for all users. https://github.com/GoogleChrome/ip-protection?tab=readme-ov-...
  3. …own tracking domains in the initial list [1] of domains they’re going to apply this to. [1]: https://github.com/GoogleChrome/ip-protection/blob/master/Ma...
  4. …signed into their Google account in the Chrome browser before starting an Incognito session." 1. https://github.com/GoogleChrome/ip-protection?tab=readme-ov-...
  5. ▲ 54
    Chrome browser bringing an IP address privacy tool to Incognito
    story by privacyWatcher · 2025-02-13 · 53 comments
  6. Well, I mean, Google is planning that for all Chrome users: https://github.com/GoogleChrome/ip-protection
    comment by marvinblum · 2024-06-05 · in Google to shut down Google One VPN on June 20
  7. ▲ 3
    GoogleChrome/ip-protection
    story by bookofjoe · 2024-05-08 · 0 comments
  8. …hop. This ensures that neither proxy can see both the client IP address and the destination. — https://github.com/GoogleChrome/ip-protection#core-requireme... If they choose to go ahead with the second hop it would be the same as Apple’s…
  9. …considering using 2 hops for improved privacy. A second proxy would be run by an external CDN ... https://github.com/GoogleChrome/ip-protection "Considering" means "we're thinking about it, but it's in no way final". Sounds like Google…
  10. Yes, but it’s end-to-end-encrypted. See https://github.com/GoogleChrome/ip-protection/issues/10 for example. Of course, Google can conceivably backdoor Chrome, and then the exfiltration of data wouldn’t be obvious from the client-side…
  11. Looks like TLS will encrypt traffic end to end, but plain HTTP would travel in the clear. https://github.com/GoogleChrome/ip-protection#core-requireme...
  12. …[...] There is an end-to-end encrypted tunnel via TLS, from Chrome to the destination server. [0] https://github.com/GoogleChrome/ip-protection#core-requireme...