Live data from Hacker News

Cloudflare Warp

1.1.1.1

61–70 of 196 posts

Re: Cloudflare Warp

#61
post #55
post #29

> Your Internet service provider can see every site and app you use—even if they’re encrypted. Some providers even sell this data, or use it to target you with ads. > We believe privacy is a right. We won't sell your data, ever. "We, the people who make up this company now, but not in the future, PROMISE." I notice they didn't say "we don't keep the data." According to the comments, this is just wireguard. I deployed…

I’m confused by the first claim. Is it really true? I thought TLS prevented anyone from inspecting my traffic. Am I completely off base?

They know what IPs you are connecting to and when, which is valuable. If Cloudflare serves the site you are connecting to (which is increasingly more common) they have access to all of the data you are transmitting.

Re: Cloudflare Warp

#62

Earlier quoted context omitted.

Unfortunately not.

>people who disagree with me shouldn’t get to use the internet Ok.

People committing several crimes are subject to denial of service. But yours is not a surprising position from someone trying to greentext here.

Re: Cloudflare Warp

#63
post #27

Earlier quoted context omitted.

Not sure what you mean - mullvad supports using wireguard?

Not sure what you mean - he never implied that mullvad didn't support wireguard. He was asking why the original commenter used OpenVPN over wireguard.

Ah, I missed that part skimming the gp post.

Re: Cloudflare Warp

#64
Can anyone explain how Cloudflare got the 1.1.1.1 domain? I know they are an influential company that controls a large portion of the internet, but I'm still confused. Is it an IP or a name that gets matched to an IP?

Re: Cloudflare Warp

#65
post #61
post #55

Earlier quoted context omitted.

I’m confused by the first claim. Is it really true? I thought TLS prevented anyone from inspecting my traffic. Am I completely off base?

They know what IPs you are connecting to and when, which is valuable. If Cloudflare serves the site you are connecting to (which is increasingly more common) they have access to all of the data you are transmitting.

Somehow I thought they meant more. I’m sure my ISP is after all of my data but I’d rather them than CF. Upon rereading their claim I suspect it is just about IPs and hostnames. I can live with that. Also my browser uses DoH.

Re: Cloudflare Warp

#67
post #64

Can anyone explain how Cloudflare got the 1.1.1.1 domain? I know they are an influential company that controls a large portion of the internet, but I'm still confused. Is it an IP or a name that gets matched to an IP?

Its an IP address.

Re: Cloudflare Warp

#68
post #64

Can anyone explain how Cloudflare got the 1.1.1.1 domain? I know they are an influential company that controls a large portion of the internet, but I'm still confused. Is it an IP or a name that gets matched to an IP?

https://blog.cloudflare.com/dns-resolver-1-1-1-1/

https://labs.apnic.net/?p=1127

Interestingly, we are now 4 years into this 5 year experiment.

Re: Cloudflare Warp

#69
post #13

Where is Cloudflare heading to? Do they want to „own“ the entire internet traffic?

Perhaps centralization is the fate of an internet where it costs $5 to boot a website off of it.

Well. I hear you. But, is it really centralization if we are adding one more ‘super node’ as we seem to be doing in this case?

I am all for even more big companies having even bigger networks. As long as they cannot stop new players from emerging and getting bigger, these centralization vs distributed trade offs are largely academic.

Re: Cloudflare Warp

#70
post #55
post #29

> Your Internet service provider can see every site and app you use—even if they’re encrypted. Some providers even sell this data, or use it to target you with ads. > We believe privacy is a right. We won't sell your data, ever. "We, the people who make up this company now, but not in the future, PROMISE." I notice they didn't say "we don't keep the data." According to the comments, this is just wireguard. I deployed…

I’m confused by the first claim. Is it really true? I thought TLS prevented anyone from inspecting my traffic. Am I completely off base?

Well with TLS it stops (almost (1)) anyone from seeing which pages you access on a site (with exceptions(2)), but which site you visit is still accessable unless the server supports Encrypted server name indication (ESNI).

When using standard SNI (SNI is used so you can have multiple domains on the same IP address) your connection to the server is not encrypted until after the hostname of the server you are requesting is sent at which point the server knows which cert to use to encrypt the rest of the traffic. So you can pull the host header out of the pre-encrypted traffic and look at which site the user is connecting too.

1) When the webserver you are accessing uses services that terminate TLS before the origin server (Cloudflare and CloudFront to name two) then the operators of those TLS terminators might be able to see which pages on that site you visit

2) You might be able to determine which page someone is accessing via side channels, for example if example.com/naughtypage.html always returns a page of a certain size which is determinable you can presume they connected to example.com/naughtypage.html if the returning data matches that size.

Post reply on HN