4 ms·
There's a phenomenon I observe quite regularly in tech. A problem exists and creative people develop an innovative solution to said problem. The solution then b
by globular-toast 6y ago
There's a phenomenon I observe quite regularly in tech. A problem exists and creative people develop an innovative solution to said problem. The solution then becomes popular and a singular goal of uncreative people who deploy said solution everywhere and push it to its logical extreme.
I remember seeing this in the mid-2000s when HTML tables were shunned in favour of "divs". I saw people reinventing tables using divs and CSS to display tabular data. Completely missing the point, of course.
This is an example of that for me. How can I possibly trust every single website I visit? It means nothing to connect to a news website, say, and see the "green padlock". Who am I trusting exactly? That I've successfully connected to some load balancer that is operated by "super-trustworthy-tech-news.com"? What's the use in that? Am I supposed to trust them more than some man-in-the-middle just because they own a domain name?
But maybe it's for privacy? If you want privacy you use tor. HTTPS does nothing for privacy when it's the same tech giant on the other end that is collecting all the data. It just means that said tech giant gets exclusive access to that data. Great.
All this does is train people to not care about security and to just trust us to do the right thing because they are too stupid to get it. Sooner or later there will be an event where a government compromises a CA. Bad luck. Some Americans already decided this was a solved problem and that this could never happen.
- bambax 6y agoCouldn't agree more. Benefits of using HTTPS for most websites are doubtful, but the costs are real, in overhead and caching problems. We don't need the same level of security everywhere. (I'm not even sure we need that much "security" in general, but that's another topic.) It's sad to see Firefox continuing to bother itself with solving non-problems while serious bugs go uncorrected for years.
- rosstex 6y agoThis comment is why people make fun of HN.
- jacquesm 6y agoTables are better as well in the sense that they are a higher level representation than divs. The problem was that people were then using tables as a way to layout pages rather than to use them to display tabular data.
- afiori 6y agoI think it is deeper, the problem is that HTML tables are serialized in row and columns separately, so for example if you wanted a cell to be 2 rows tall and 2 columns wide there wasn't a local change that could allow it. To my understanding CSS Grid is meant to solve this
- afiori 6y ago> Am I supposed to trust them more than some man-in-the-middle just because they own a domain name? The green padlock will not turn any unreliable fake news site of your choise in a trustworthy outlet but it does make some guarantees about it being the same site as yesterday (barring security leaks or missed DNS renewal) AFAIU the elefant in the room is that if your DNS resolver is malicious and points all domains to a malicious IP then https is completely useless.
- globular-toast 6y ago> but it does make some guarantees about it being the same site as yesterday No it doesn't. Are you thinking of TOFU via public key pinning?
- afiori 6y agoI was oversimplifying my limited understanding. What I belive should be true is that you are connecting to a server that: 1. managed to obtain a valid certificate from some recognized autority 2. managed to steal a valid certificate for the domain in question from another server 3. managed to convince enough DNS resolvers to point to their IP for a given domain (so to get your traffic and/or pass LE challenges) and/or other conditions. From an operational perspective it says very little, especially considering the third case where any public wifi network has in most cases total initial control over your DNS traffic.
- josephcsible 6y ago> if your DNS resolver is malicious and points all domains to a malicious IP then https is completely useless. 100% false. HTTPS absolutely protects against that.
- kevincox 6y agoHTTPS ensures the following things 1. You are talking to the domain that you think you are. 2. No one else can see the traffic in transit. 3. No one has modified the traffic. It does not provide any guarantee around the trustworthiness of the domain itself. (Well EV Certs try but as far as I am concerned that is worthless.) 1 and 3 are not helpful in your example of "Am I supposed to trust them more than some man-in-the-middle" but it does help once you establish other trust in that domain. For example a friend sent you the link, or you start using the site regularly. However personally even just 2 is a tangible benefit when I am using public connections. I very much like the idea that my browser will not send out an unencrypted data without my explicit approval.
- robertlagrant 6y ago> Am I supposed to trust them more than some man-in-the-middle just because they own a domain name? You can be assured that you are actually talking to them. That's a big step up from not being able to do that.
- perryizgr8 6y agoDepends on the content of the website. A lot of websites wouldn't benefit at all from that assurance. A lot of blogs and random personal projects come to mind. My own blog does not care about authentication or MITM at all. It would be just an unnecessary complexity without any benefit.
- robertlagrant 6y agoIt's not the websites that get that assurance. Maybe read up on it.
- perryizgr8 6y agoI do understand that.
- bullen 6y agoThank You!