4 ms·
95% of the internet traffic is now TLS according to Google: https://transparencyreport.google.com/https/overview?hl=en https://transparencyreport.google.com/ht
by dmix 6y ago
95% of the internet traffic is now TLS according to Google:
https://transparencyreport.google.com/https/overview?hl=en https://transparencyreport.google.com/https/overview?hl=en
Most of the most severe attacks require HTTP and physical proximity. So we’re fortunate of the huge drive towards HTTPS since Snowden’s 2013 releases when it was around ~55% (I’ve seen the rise in numbers correlated before).
But it also recommends upgrading your router. I wonder how many routers and IoT device companies are actually releasing firmware updates. And quality ones at that…
- BeefWellington 6y agoTLS is useful and should be the default for everything; However, it is not the protection everyone seems to assume it is for several reasons: 1. Users generally still click "Accept & Continue" when they see certificate warnings. 2. A given app can easily disable certificate validation and blindly trust the other end. For web browsers, great they do it well. Other applications often disable certificate validation altogether. Plenty of mobile apps I've seen fail to do proper certificate validation, though thankfully it is becoming less common thanks to vendor platforms removing the option to be horribly insecure. 3. An attacker can still see which domain names and/or hostnames you're accessing. The simplest useful thing I could think of with this might be is finding a given WiFi network's IP on the Internet, in those circumstances where the hardware permits you to create your own frames.
- tialaramex 6y ago> 1. Users generally still click "Accept & Continue" when they see certificate warnings. In Firefox HSTS blocks this entirely. There is no "Accept" option at all. In Chrome HSTS means the only way to "accept and continue" is to type whatever the current magic bypass phrase is, the ordinary "accept and continue" option isn't there.
- grishka 6y agoAnd even without HSTS, most web browsers bury the option to continue deep enough that for most users it could as well not exist. In Chrome you have to click "details" and there will be a tiny link to "continue anyway".
- 0xbadcafebee 6y agoThis is a vulnerability more than a benefit. If you need to access a website and can't because of ominous errors, most users will simply try a different device. If the user always browses a specific site on their desktop, and the desktop hits an HSTS warning, the user will immediately try it on their phone, which has never visited the site, and thus has no HSTS record, and will then click through any certificate warning. As far as the user is concerned, the website or their internet connection (or both) are just screwed up. Web browsers have never taken any of this seriously. Their hilariously poor UX around errors and warnings, their half-baked mitigation schemes, their reluctance to figure out new industry solutions for extremely common problems like setting up a wireless access point, etc.
- toast0 6y agoIf you (as a site owner) care about HSTS, you'll likely get your site included in the preload list, which closes the other device loophole for the most part. (There certainly are some devices with browsers that don't get updates and/or don't do HSTS preload, but can't fix everyone).
- 0xbadcafebee 6y agoThe preload list is another crap web browser mitigation. "Hey, we have this problem with our browsers where the security is trivially defeated a number of ways. What are we gonna do about it? ......... I got it! We'll make extra security optional!" As a regular web user, I should be able to know if the site I'm using is secure from MITM. But that's basically unknowable, because for any given site you're on, there may be a half dozen different kinds of duct tape implemented in different ways. I just have to hope nobody wants to hack me. All the mitigations might as well not exist.
- Bulpi 6y agoI'm already disagreeing with your main point 1) My parents don't know how to do this and would call me and stop trying to 'solve it' Chrome and Firefox are quite visual in this regard.
- foobarbecue 6y agothisisunsafe...
- Wowfunhappy 6y ago> Users generally still click "Accept & Continue" when they see certificate warnings. I am one of these users. However, that doesn't mean the warning isn't useful—it puts me on high alert! I enter these websites knowing that I shouldn't trust any information I see, and that I shouldn't enter anything important. I am of course more technically inclined than the average user, so I don't know that my behavior is broadly applicable. Even so, I wonder if this metric necessarily means what it seems to mean.
- petjuh 6y agoAnd the drive to HTTPS was initiated by "evil" Google (like free email with >2GB which was unheard of at the time).
- Fnoord 6y ago> like free email with >2GB which was unheard of at the time If its free, you're the product. Yet people don't know. Call me old fashioned but I rather pay for my e-mail services.
- KMnO4 6y ago> Yet people don’t know. I’m not sure that’s true. Many people know and simply don’t care. Using hypothetical me as an example, why does it matter to me that Google can read my emails? Why does it matter to me that Google is improving their searches by tracking my activity? I’ve got nothing to hide. And before you say “I’ve got nothing to hide” isn’t a good reason to give up privacy and freedom... well that fight isn’t here on HN. It’s a fight with the hundreds of millions of privacy apathetic people who are winning the fight by a landslide. We can hate on FANG as much as we want, but if 2/3 of the population can validate their business model, does it even matter?
- sharot4 6y agoI think that most people implicitly assume that their communications are private. Mass surveillance is an open secret that is easier on the senses to ignore. Ignorance can be combatted with information. But now there's a "war on information" with companies like facebook (in true comedic fashion) being the arbiter of "truth". Facebook, one of the biggest players in the mass surveillance game. The business model is validated because of ignorance. Most people have no idea what pixel tags are, for instance, yet the web is oozing with them. When given the option, people prefer not to be surveilled. It is more or less inhuman to want to be watched surrepticiously. We call that stalking.
- tialaramex 6y ago> If its free, you're the product. I'm not sure this is even useful as a rule of thumb, let alone generally true. Let's Encrypt certificates and Debian are both "free" in the sense you mean, are you somehow "the product" for those? Everywhere I'm aware of in the world, COVID-19 vaccines are free, are you "the product" when immunised against a deadly disease? How so? Air is free, am I the product for like... trees? How does this work? And in contrast it's pretty clear that many expensive things Americans buy treat them as the product anyway, because it's free revenue. So the rule of thumb doesn't even help you to avoid being scammed, it just means you're more willing to pay for the chance.
- tialaramex 6y agoThose figures are for Google's services, so all those services can do TLS, but some of the clients don't. However the step change for HTTPS over the wider web is mostly a bunch of related mutually enabling changes: * Let's Encrypt launches * Google slightly penalizes plaintext HTTP in search * Browsers (Chrome, Safari, Firefox at least) stop offering new features outside Secure Context (so HTTPS for public sites) and begin deprecating or reducing scope of some older features outside that context. On smaller sites also don't underestimate * Prevalence of browsers/ devices without SNI falls a lot so... * Many bulk hosting sites begin offering cheap or free HTTPS virtual hosting, with SNI, where previously they only offered IP hosting for HTTPS at higher prices. In 2005 if I wanted my new one-joke web site to have HTTPS that's a bunch of extra money, for one corny joke, it's not worth it. Today, it's zero extra effort, if I make a new site it has HTTPS by default of course. If I see somebody whose host is trying to charge them money for this, these days it's rarely worth chipping in "You are being ripped off" because somebody else will be typing that already.
- commandlinefan 6y ago> the most severe attacks require HTTP Well, for the services that use HTTP, anyway - there's still a lot of non-HTTP traffic out there like SMTP and DNS. Devices still use SNMP, too, and often connect over wifi.
- huachimingo 6y agoLike with every old phone: they will not patch it. Then they will tell you to buy a new one or a similar but new model.
- fpgaminer 6y agoOnce someone is on your LAN, HTTPS isn't the end-all-be-all protection. If, for example, a website hasn't enabled HSTS, or they have but they don't have HSTS preload and the user hasn't visited them before.
- fomine3 6y agoThat's why TLS for internal network/IoT devices is important. Browser industry must seriously consider this uncovered usage.
- nanis 5y ago> huge drive towards HTTPS since Snowden’s 2013 releases Note that HTTPS everywhere in conjunction with HR 4681[1] means there are no limits on how long US government can retain captured communications of US citizens: > Covered communication.–The term ``covered communication’’ means any nonpublic telephone or electronic communication acquired without the consent of a person who is a party to the communication, including communications in electronic storage. > … > Limitation on retention.–A covered communication shall not be retained in excess of 5 years, unless– > … > the communication is enciphered or reasonably believed to have a secret meaning; [1]: https://www.nu42.com/2014/12/https-everywhere-and-hr4681.html https://www.nu42.com/2014/12/https-everywhere-and-hr4681.htm...