zlacker

Warp isn't trying to "hide your IP from the sites you are visiting". It's there to help prevent intermediaries from observing your traffic. A huge percentage of the web is still unencrypted HTTP.

And Warp+ aims to be about that plus performance.

If you want to be totally anonymous on the Internet then I recommend you use Tor. If you just use a VPN then you may hide your IP address from sites you visit but there are tons of other fingerprinting techniques that can be used.

>>jgraha+(OP)
I understand all that, and you didn't answer my question. Why do you push the narrative that 1.1.1.1 DNS resolver protects user privacy (by hiding originating IP / subnet) whereas 1.1.1.1 VPN gladly reveals that data? In both cases, the destination is hidden to any eavesdroppers, but in the latter case (VPN) the source IP is visible to the destination website, whereas you keep insisting how vital it is to hide source IP in the former case (DNS).

>>tomp+X4
In the case of Warp, we add the connecting IP information as a header to the HTTP request for sites on Cloudflare. This will typically be inside TLS to the origin server, and so the source IP information will be encrypted and only visible to the web site being visited.

In the case of DNS information about the subnet, the query etc. is sent around unencrypted.

One is open to eavesdropping, the other is not.

>>jgraha+H7
Someone capable of eavesdropping on that query sure as hell capable of eavesdropping on incoming connections to 1.1.1.1 where they can see actual IP address that initiated the query. There is no way to justify this as a privacy feature. Well, unless people don't understand enough to believe you.

>>zzzcpa+29
Not really. An eavesdropper can sit in front of the authoritative server for a site and eavesdrop on all the DNS queries with EDNS information. That's one place they need to be.

To eavesdrop on Warp you'd need to do it all over the world, capture encrypted traffic and then try to correlate traffic. If your threat model is a global adversary capable of doing that correlation and you don't want sites to know your IP, then use Tor.

>>jgraha+qa
> An eavesdropper can sit in front of the authoritative server for a site and eavesdrop on all the DNS queries with EDNS information.

No, they can sit near your 1.1.1.1 servers and catch all incoming and outgoing traffic, watching connections to your 1.1.1.1 servers that initiate DNS queries and actual outgoing queries that 1.1.1.1 makes to authoritative servers and responses too.

>>zzzcpa+ub
So if we're talking just about unencrypted DNS to 1.1.1.1 then you're assuming an entity capable of sitting in front of us in 194 cities worldwide.

vs

With EDNS sitting in front of the authoritative server of the site this actor is trying to monitor.

The latter is easier than the former.

>>jgraha+Pc
In the latter case it's just as easy to catch real IP addresses by sitting in front of authoritative DNS servers and actual servers those DNS records point to. As I said, you just can't justify it as a privacy feature. It does nothing significant in any threat model.

>>jgraha+H7
Ok, that makes more sense. So you're basically worried about the unencrypted connection between Clouflare and DNS authority server. Initially I understood that you're worried about leaking IPs to DNS authority server itself.

>>jgraha+H7
On twitter[0], they claimed the main thing they were after is a very rough geolocation with the dns request. Country level, or at least continent level. So they can respond with a nearby data center.

That doesn't sound too bad, privacy-wise.

EDIT: I mean if you were to map all US IP's to a single canonical IP for instance.

[0] https://twitter.com/archiveis/status/1018691421182791680