3 ms·
> I also think the MITM risk is overrated compared to how much barrier HTTPS creates to accessing basic information. That's not the only attack TLS is trying t
by bawolff 4y ago
> I also think the MITM risk is overrated compared to how much barrier HTTPS creates to accessing basic information.
That's not the only attack TLS is trying to thwart (although it is a major one). Passive surveillance resistance is also a big use case of TLS.
I think the biggest thing though, is everyone has pages that are sensitive some of the time (e.g., I want to visit my bank over TLS). It is really really difficult UI problem to give people actual security when TLS is only on some of the time. Users never really understand how the security stuff works, and it is usually trivial to trick them unless you basically do forced TLS everywhere. Its also hard to know what is sensitive to users as it varies by place (e.g. Tianamin square article on wikipedia. Maybe in other places, websites about abortion, etc. Some places nobody cares if you look that up. In other places it is a big deal. Difficult to make things secure only for the users where it matters.)
- prepend 4y ago> Passive surveillance resistance is also a big use case of TLS. For much of the internet this is not protected as people use Chrome that performs passive surveillance. For me, I’ve accepted passive surveillance for routine day to day activities. So I don’t care if my http traffic is analyzed by Starbucks or anyone. My TLS traffic is deep inspected by google through chrome, at work it’s literally MITM’d and inspected by IT, and at home the dns data is tracked by my ISP or google or maybe not cloudflare depending on my DNS, and otherwise inspected through host headers by my ISP and everyone in between. I don’t think this is even a factor in deciding if my site is http or https.