Because HTTPS protects only things you do on the site. ISP still knows which sites you connect to. Which YouTube video you are watching to. etc. F.E. in Russia ISP’s have to keep logs of users interactions for half of year and give it to government when they need them.
Your ISP won’t know what video you’re watching, only that you’re accessing data from youtube.com and other domain names.
That’s not a problem for most generic websites, but authoritarian governments probably won’t like you visiting any domain that looks like wikileaks.com or voanews.com.
My opinion. I can’t trust any government on this planet anymore. So much fuck ups and stupid decisions. So basically every government is kinda authoritarian for me…
Yes, because they know the IPs your packets go to, but if there are multiple websites behind a single IP they won’t know which one (unless you use your ISP DNS server, which you should probably not)
Which YouTube video you are watching to. etc.
No, because the URL is contained within the HTTP packets which are encrypted with SSL (the S in HTTPS), so unless the ISP does MiM, they cannot know which URL you are visiting.
Yes, because they know the IPs your packets go to, but if there are multiple websites behind a single IP they won’t know which one (unless you use your ISP DNS server, which you should probably not)
That’s not true. Almost all TLS clients use SNI to send the server name in plaintext, so the server can present the right certificate. With QUIC/http3, this is no longer done in plaintext, but the packet is still being sent alongside the initial encryption key so anyone with access to the traffic can simply decrypt these packets.
There are trials out there for ESNI/ECH, which encrypts the SNI fields in a way the ISP can’t read, but those are far from stable, not implemented by most web servers, not enabled by default by web browsers, and require additional setup for website admins (read: won’t be widely implemented for another five to ten years).
The URL and Host header are encrypted of course. Your ISP can find out you’re going to youtube.com, but not what video you’re watching.
Oh, thanks for this precision, I wasn’t aware of this. And now that I think of it, it’s obvious that the first exchange with a server has to be unencrypted
Because HTTPS protects only things you do on the site. ISP still knows which sites you connect to. Which YouTube video you are watching to. etc. F.E. in Russia ISP’s have to keep logs of users interactions for half of year and give it to government when they need them.
Your ISP won’t know what video you’re watching, only that you’re accessing data from youtube.com and other domain names.
That’s not a problem for most generic websites, but authoritarian governments probably won’t like you visiting any domain that looks like wikileaks.com or voanews.com.
My opinion. I can’t trust any government on this planet anymore. So much fuck ups and stupid decisions. So basically every government is kinda authoritarian for me…
Yes, because they know the IPs your packets go to, but if there are multiple websites behind a single IP they won’t know which one (unless you use your ISP DNS server, which you should probably not)
No, because the URL is contained within the HTTP packets which are encrypted with SSL (the S in HTTPS), so unless the ISP does MiM, they cannot know which URL you are visiting.
That’s not true. Almost all TLS clients use SNI to send the server name in plaintext, so the server can present the right certificate. With QUIC/http3, this is no longer done in plaintext, but the packet is still being sent alongside the initial encryption key so anyone with access to the traffic can simply decrypt these packets.
There are trials out there for ESNI/ECH, which encrypts the SNI fields in a way the ISP can’t read, but those are far from stable, not implemented by most web servers, not enabled by default by web browsers, and require additional setup for website admins (read: won’t be widely implemented for another five to ten years).
The URL and Host header are encrypted of course. Your ISP can find out you’re going to youtube.com, but not what video you’re watching.
Oh, thanks for this precision, I wasn’t aware of this. And now that I think of it, it’s obvious that the first exchange with a server has to be unencrypted
Hmm… You have way better knowledge than I am. It seems so. Should think about this things some time later 😉
deleted by creator