8 ms·
HTTPS provides more than just privacy
- nailer 11y agoAuthor here! Surprising thing when researching this was how fast some of the stuff talked about a year ago is already upon us in the upcoming browser releases: - If you're running Chrome Canary, try visiting http://html5demos.com/geo http://html5demos.com/geo (which hasn't yet been updated for HTTPS yet). Geolocation fails, consistently over HTTP - Firefox nightlies has already started warning for sites that allow POST over HTTP: https://www.fxsitecompat.com/en-CA/docs/2015/non-https-sites-containing-login-form-will-be-marked-insecure/ https://www.fxsitecompat.com/en-CA/docs/2015/non-https-sites... (for type=password only, see dsp1234's note below) PS. since this article has gotten so much attention: does anyone on HN know of a newer app than Driftnet or Etherpeg for reassembling images from HTTP traffic? I wanted something newer (that people could install themselves on a Mac) but couldn't find anything.
- Dorian-Marie 11y agoThe geolocation demo works on Chrome for Android though.
- dsp1234 11y agoFirefox nightlies has already started warning for sites that allow POST over HTTP only for pages that contain a password input
- cpeterso 11y agoHere is the Chrome bug report to remove geolocation support for insecure origins (in Chrome 50): https://codereview.chromium.org/1530403002/ https://codereview.chromium.org/1530403002/ And here is the Firefox feature request, filed in 2014: https://bugzilla.mozilla.org/show_bug.cgi?id=1072859 https://bugzilla.mozilla.org/show_bug.cgi?id=1072859
- datalist 11y agoWhile the point of the article is not incorrect, I would say the title is #0 and #1 are intrinsically part of HTTPS #2 and #3 are just because Google and browser vendors simply limit these things to HTTPS. It is not like it can only come with HTTPS. Finally, #4 is a side effect of #0. So the only thing really provided BY HTTPS is encryption and authenticity.
- nailer 11y agoI see your point - many of these are side effects of encryption - but the reason I (the author) wanted to focus on some of these things, particularly 2, 3 and 4, is that people don't realise there may be problems they encounter from not using HTTPS, even if privacy wasn't their main concern. E.g, you run an online video company, and (for some silly reason) you don't care about privacy. You still don't want T-Mobile turning your great HD content into a low resolution blocky mess. Edit: actually, thinking about it, you're right. I've updated the article to use the word 'privacy' to better separate it from the other aspects on encryption. Thanks datalist!
- vtlynch 11y ago>#2 and #3 are just because Google and browser vendors simply limit these things to HTTPS Seems like a pretty real and legitimate reason to me.
- untog 11y agoSeems like a pretty real and legitimate reason to me. Sure, but HTTPS doesn't provide it. I mean, not really. HTTPS is the flag by which browser manufacturers have toggled the behaviour.
- ybx 11y agoHTTPS doesn't directly provide it, sure, but it's still a benefit you get when using HTTPS. This is just pedantic.
- JoshTriplett 11y ago> #2 and #3 are just because Google and browser vendors simply limit these things to HTTPS. It is not like it can only come with HTTPS. True for "signaling value", but for powerful browser features that the user grants or denies on a site-by-site basis, there's a critical reason to only allow those for HTTPS. If you allow those features for HTTP, you allow them for anyone who can MITM your connection and spoof those sites. Any random ISP, open wifi, or other entity could trivially MITM a popular site via HTTP and obtain privileges it should not have.
- overcast 11y agoAlso provides heartache and headaches to get working properly.
- r1ch 11y agoand significantly lower ad revenue for ad-supported sites.
- jimktrains2 11y agoHow so?
- nailer 11y agoSome of the ad networks don't have https support yet. Though this is really the fault of the ad networks, and since they want customers, will probably be resolved soon.
- tomjen3 11y agoThat honestly sound like they aren't interested in being in business for long then. I mean how can you not have SSL support when the major businesses will be your customers?
- cpeterso 11y agoThe IAB is promoting a "LEAN" ads: Light, Encrypted, Ad choice supported, Non-invasive ads. Given that all of these recommendations go against the current trajectory of advertising, I doubt they will be adopted any time soon. http://www.iab.com/news/lean/ http://www.iab.com/news/lean/
- lorenzhs 11y agoIt's easy to get a good configuration for popular servers from https://mozilla.github.io/server-side-tls/ssl-config-generator/ https://mozilla.github.io/server-side-tls/ssl-config-generat... and certificates are really easy to get from Let's Encrypt, both with the official client or others such as acme-tiny or simp_le if you don't like the official one. Headaches are not an excuse any more.
- pilif 11y agoEspecially point 4 («Not having your content modified by carriers») is getting more and more important these days. Whenever I hear people saying that they don't need https as they are providing a strictly read-only experience I always wonder what they will say as their ads get replaced with other ads by carriers and other "transparent" proxies in between. And if your site is only moderately complex and using some of the more advanced HTTP features (pipelining, websockets or plain long polling), you might be better off using SSL too because by now the likelyhood of any of this working unhindered by various "security" and "traffic optimization" tools is approaching zero very quickly. On the other hand, I wonder how long it's going to take before carriers and providers in general mandate the installation of a root cert "for your security" in order to be able to continue messing with the traffic to insert ads or "increase security".
- sigmar 11y agoTo reiterate your point. I've used free/complimentary wifi that overlays ads (specifically: megabus wifi). It is awful and even made some sites difficult to use. My solution at the time was to use a VPN, but it would have been nice if I didn't have to resort to that.
- Washuu 11y agoI have that problem with Comcast and their data cap notifications being injected into HTTP web sites. Yesterday I called them and agreed to pay their $35 extortion fee to get "unlimited" data along with being removed from their proxy system. :/
- gruez 11y agowouldn't it be cheaper to get a $5/month vpn/vps?
- FireBeyond 11y agoThat doesn't get you out of Comcast's cap system.
- 11y ago
- Flimm 11y agoHere's another reason: If you're providing iframe or Javascript embeds for people to paste on other websites, (like YouTube and Vimeo do for their videos), you better be using HTTPS. If you don't, your embeds won't work on HTTPS sites, as modern browsers block mixed active content.
- Grue3 11y agoYeah, it also provides stable profit to certification "authorities".
- _ikke_ 11y agoNot with initiatives like letsencrypt.
- narrowrail 11y agoAs _ikke_ mentioned, it's as if you entirely missed the HN discussions about LE. https://en.wikipedia.org/wiki/Let's_Encrypt https://en.wikipedia.org/wiki/Let's_Encrypt You can also search HN and GitHub to discover the numerous features and tools.
- Grue3 11y agoLet's Encrypt is essentially shareware. The basic features are available for free, but if you want something better than that, such as wildcard certificates, you must pay up. Not to mention that it's cross-signed with IdenTrust, a commercial CA, and since everyone on the web has to use this service to get HTTPS (there aren't other decent alternatives), this is a good way for IdenTrust to boost its numbers and be able to claim it's "the biggest CA in the world" or something. There's no way to choose a different CA with Let's Encrypt.
- matt4077 11y ago- Why should I care about the backing CA as long as all browsers accept it? - You can register up to 100 subdomains in a certificate and up to 5 certificates per domain/week. With their certificate expiry set at 3 months, that comes out to about 6,000 subdomains you can register. I know there are some setups where every user gets a subdomain. But I'd wager that less than 1 in 10000 LE users would run into these limits. (which may actually be lifted when the beta period ends). - LE doesn't offer any paid certificates so it's really hard to spin this as a shareware-style incentive to spend money with them.
- 11y ago
- jimwalsh 11y agoFunny that this article about HTTPS gets a Red X on the https in my Chrome.
- nailer 11y agoHi Jim! We're confident the site is properly configured https://www.ssllabs.com/ssltest/analyze.html?d=certsimple.com https://www.ssllabs.com/ssltest/analyze.html?d=certsimple.co..., but if you email me mike@certsimple.com with details of any errors I'll happily check it out.
- deleted 11y ago[deleted]
- ultramancool 11y ago> T-Mobile degrades video quality SSL cannot prevent this. The connection can still be slowed down and video quality will be automatically degraded. They don't reencode streams on the fly or anything, just degrade bandwidth and let the applications do the rest. The reencoding and DRM cracking needed to do the former would be an insane investment of man-hours and CPU resources, even if they didn't use SSL. Additionally a bunch of these "reasons" are just artificial restrictions imposed by web browsers. If it weren't for letsencrypt providing free certs without any ID checks like other free cert places I'd be complaining about it.
- nailer 11y agoYeah, I think in this case T-Mobile was re-encoding anything in HTTP, so the stream appeared to be full quality but wasn't. Simple QoS would keep the quality down and the bandwidth low, but hopefully it would be more apparent that a better quality stream exists but is not being delivered.
- ikeboy 11y agoDo you have a source for that? The article you linked doesn't say that, and https://www.eff.org/deeplinks/2016/01/eff-confirms-t-mobiles-bingeon-optimization-just-throttling-applies https://www.eff.org/deeplinks/2016/01/eff-confirms-t-mobiles... also confirms that no encoding is taking place. Separately, the article you linked from techdirt has a major misunderstanding of the EFF piece. It says "EFF also discovered that T-Mobile's earlier statement that it can't detect encrypted video is also misleading, as the company now claims it can" But the EFF part quoted is talking specifically about http, not https, as a close reading will reveal. Also, the EFF test is a bit inconclusive, because https might be slower than http for other reasons. It probably doesn't account for the large differences they observed, but a better study would have tested http/https on other carriers, and on a T-mobile phone with Binge On turned off, to isolate the Binge-on effect.
- fryguy 11y agoIf you look at the chart about halfway down, the "Normal" (red) is HTTPS, and the "Binge-on" (blue) is HTTP.
- ikeboy 11y ago>T-Mobile re-encodes videos, degrading quality The link goes to an article that says T-mobile didn't reencode at all, but was throttling. I don't think there's any evidence that T-mobile re-encoded video from non binge-on providers, so they don't belong in that list. (And if someone's a partner, they want to help T-mobile do whatever it is they're doing, so using https to prevent that makes no sense.)
- stygiansonic 11y agoMaybe a nitpick, but I think this section could be clearer: "Except HTTPS traffic won't show up on Malory's screen: things encrypted with a website's public key can only be decrypted with the website's private key. Because the website's private key is (hopefully) only available to the website, Malory can't decrypt the traffic." I know it's just an overview, but this explanation seems a bit confusing. I mean, it's true that the trust is anchored on the private key but that's only one part of it. My (simple) understanding of TLS is that basically, the public/private keys are used to secure the shared secrets used to derive the symmetric session keys OR to authenticate something like a DH key exchange that's used to derive the session keys. In the first case, the client would generated a shared secret, encrypt with the public key, and then send to the server. In the second case, the authenticated DH key exchange allows both client/server to arrive at the shared secrets. In either case, it's these symmetric session keys which are used to encrypt/decrypt the traffic. My understanding is that even if you capture the encrypted traffic and then later on, you obtain the private key, you wouldn't be able to decrypt the traffic if the parties used something like a DH key exchange. (This would be (perfect) forward secrecy?) Of course if you have the private key and no one knows yet, then you could impersonate the server and MiTM future connections, I think. Someone with better knowledge could explain this better.
- bmm6o 11y agoYou're comments are correct, but I don't think replacing the 1 brief paragraph in TFA with your 3 would improve the article.
- flubert 11y agoWhere is a good site for getting an introduction on what HTTPS covers. Is the URL completely exposed? Does your ISP/third-parties know the domain, the subdomain, the path, and parameters in each URL?
- rogeryu 11y agoWhat I understand is that URL is encrypted, including path and parameters in URL and in POST requests. However, the IP address is public, and it's probably quite easy to link an IP address to a website. There are several websites that offer this service: search an IP and get a list of all known websites that use that IP. A link to an article from an authority in this field, that really explains this, would be really welcome!!!
- comex 11y agoThis used to be correct, but modern SSL clients support SNI (Server Name Indication), which involves sending the exact hostname in the clear to allow vhosts to have different certificates. The path and everything else in the actual HTTP request is still private, though.
- wepple 11y agoThink of it as occuring between TCP and HTTP. So you browser establishes a network connection to example.org, then negotiates to speak SSL/TLS, and then all the web things happen over the top of that (there are minor exceptions for vhost TLS configs). So no web traffic should traverse in the clear - the URL, domains, GET data, POST data, headers, etc are protected. however that does leave a surprising amount of info. Your IP address, the IP address you're connecting to, the host domain you're connecting to if your browser just did a DNS lookup (99% likely it did), how long you communicate with that site, the traffic shape, etc etc. As a crude example: your ISP sees a DNS lookup to pornhub.com, followed by a connection to the IP address associated with that name, followed by 3 hours of fairly large packet sizes in regular repetitive patterns. It's highly likely they can extrapolate what's in your browser.
- Nullabillity 11y ago
- lambau 11y agoHTTPS is especially important for Tor users. With tor, all HTTP requests pass through a random exit node, who may be malicious. If the site is not using HTTPS, then the exit node can inject malicious javascript into the page. By deploying HTTPS, you are also helping tor users to browse the web more securely.
- smegel 11y ago> This is effective enough to the point where nefarious carriers have asked users to install configuration profiles to add the carrier's root certificates, which are used to modify and inspect what should be private traffic. It makes me wonder if the NSA isn't also whispering "that would be nice" into the carriers ears.
- deleted 11y ago[deleted]
- SFjulie1 11y agoLet's imagine I am the swimming pool around the corner or the guy wanting to go to the swimming pool. Why would we need https? Who is gonna tamper the "advertisement less" schedules of the swimming pool from rue st Hubert (montréal)? Why would they? Why would the swimming pool care to pay X$/month for this? And why could I care that anyone knows I am looking at the opening and closing of my swimming pool? I am an old man, I don't watch porn or pick up on girls anymore or think of revolutions. I clearly need no https ... Why should I pay directly or indirectly for it?
- dragonwriter 11y agoWho is going to tamper with nonsensitive pages? People injectibg, e.g., malware-loading "your computer has a virus" popups.