Re:Chrome is deploying HTTP/3 and IETF QUIC
by mumblemumble on Wednesday October 07, 2020 @02:30PM
(#24711161)
Assuming your physical therapist has their own website with its own doman, and not just, say, a Facebook page, you're leaking that information to your ISP with https, too. https doesn't hide the domain you're talking to, just the specific URLs within that domain.
Re:Chrome is deploying HTTP/3 and IETF QUIC
by iso1210 on Wednesday October 07, 2020 @03:55PM
(#24712037)
We have SNI. Now sure your therapist may run their own VM on it's own IP address, but that's not very likely.
Re:Chrome is deploying HTTP/3 and IETF QUIC
by mumblemumble on Wednesday October 07, 2020 @04:14PM
(#24712217)
SNI doesn't encrypt the desired hostname in the payload of the initial connection. It's still plainly visible to an eavesdropper. They can also observe un-encrypted DNS lookups.
Re:Chrome is deploying HTTP/3 and IETF QUIC
by skissane on Wednesday October 07, 2020 @07:03PM
(#24713835)
eSNI is going to fix that
Re:Chrome is deploying HTTP/3 and IETF QUIC
by kube-system on Wednesday October 07, 2020 @02:14PM
(#24711010)
Chrome and derivatives display "! Not secure" in the omnibar, which is presumably what they are referring to.
Your browser might flag a http server as dangerous (mine doesn't - it just has a padlock with a line through), but you're leaking information to your ISP that you are reading about a Physical Therapist.
If your site tries to do https and fails (self signed or invalid certificate) it will rightly flag up that it's a problem.
My grandma would not be able to manage a server on the internet, let alone responsibly manage it. If you can't set up a modern server with https then you shouldn't be running a server on the internet at all.