Google is forcing you to use their proxy (build your own instead)

About this video

The creator explains proxies in the context of Google’s planned Chrome IP Protection feature, which he calls its Privacy Proxy. He defines a proxy as a middleman server: websites see the proxy’s IP instead of yours, hiding the persistent tracking that an IP address enables, unlike cookies you can opt out of. He contrasts this with a VPN — a VPN encrypts traffic in a tunnel, a proxy normally just forwards it, making proxies faster and lighter to host. He then questions trusting Google as that middleman, noting the man-in-the-middle-like position, the risk of a single proxy fleet being hacked or DDoSed as a single point of failure, and disruption to existing web defenses. He summarizes Google’s stated mitigations from its documents: required Google-account authentication with tokens, blinded signatures so traffic is not tied to identity, token rate-limiting and expiry, and a possible future two-hop design where a second proxy run by a CDN would mean neither hop sees both client IP and destination. He also notes Google’s proxy would assign IPs reflecting your coarse location for legal/content reasons, so it would not let you appear in another country. As an alternative he builds his own proxy on a $5/month Linode by Akamai Ubuntu server in Osaka: an SSH SOCKS tunnel using ssh -D on port 1337, then pointing Firefox to localhost on that port, which makes his IP appear in Japan. He repeats the process with Shadowsocks from the Linode marketplace — a server in Mumbai, port 8000 and AES-256-GCM encryption in the config he shows — and a Windows client set to global system proxy, giving proxy routing plus encryption.

Key takeaways

• A proxy hides your IP by having websites see the proxy server’s IP instead; a VPN does that plus encryption, at a speed/resource cost
• The creator’s concern with Google’s proxy is concentration: one provider in the middle creates hack, DDoS, and single-point-of-failure risks
• Google’s proposed safeguards he cites include authenticated tokens, blinded signatures, rate limits, and a possible second non-Google hop
• The simplest self-hosted proxy needs no extra proxy software: SSH to a cheap VPS, run an SSH -D SOCKS tunnel, and set your browser to localhost on that tunnel port
• Shadowsocks is presented as the more robust self-hosted option: easy VPS marketplace install, clients for desktop and mobile, and encrypted traffic

Episode details: published November 22, 2023 · 15:05 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are NetworkChuck’s own claims, shared for education — they are not typical or guaranteed.

← Previous: Put your website on the Dark Web · Next: the most secure OS in the world…..I hate it →

All NetworkChuck videos · NetworkChuck profile · NetworkChuck on YouTube