7 ms·
I don't understand why I need to use https on a static marketing webpage. No login stuff, no JavaScript, nothing. Just straight up HTML and CSS. Right now I nee
by Kiro 10y ago
I don't understand why I need to use https on a static marketing webpage. No login stuff, no JavaScript, nothing. Just straight up HTML and CSS. Right now I need to pay about $150 every year for something that's only used to satisfy Google PageRank (I can't use LetsEncrypt with my hosting provider). Why?
- Nullabillity 10y agoYeah, why are you using a bad hosting provider?
- Kiro 10y agoLegacy and one of the only hosting providers in my country. I don't want to risk worse localized SEO by hosting it outside.
- RossM 10y agoI've been reading up on localisation SEO lately - as far as I understand, Google only uses "server IP is located in X country" as an indicator of where a site might be localised for, if it can't get any better information. For example, if you're using a ccTLD for the domain, or if it's a generic-TLD and you declare a country in Google Webmaster Tools, that will be a much stronger weighting. Of course, if that's wrong I'd love to know!
- Kiro 10y agoThank you. The actual web app is hosted on Linode in Frankfurt (using LetsEncrypt for https) so maybe I should host the marketing page there as well if that's true.
- djsumdog 10y agoWhen I was in the EU, I saw both Vodaphone and Three inject banners on the top of websites in various countries. They're not as easy to get away from as you think.
- eganist 10y agoKeeping it extremely high level: Among other reasons, not encrypting traffic gives an opportunity for bad actors to replace content in transit to your end users when your end users are on compromised connections, such as rogue "free" wifi networks in airports or coffee shops, or even legitimate networks which have in some way been compromised, e.g. the ISPs of the world who decide to inject other content e.g. their own ads into unencrypted traffic. The next question is usually "what could they possibly do, change a few pictures?" They could inject malicious payloads, and for all your users would know, it would appear to them that it came from your site. > I can't use LetsEncrypt with my hosting provider Consider switching. For a static site, consider Gitlab; they do a good job of permitting LetsEncrypt. --- I sincerely appreciate the question, though. I have marketing people ask me this question all the time in private who hesitate to do so in public because quite a few security types berate them for not doing something "obviously" more secure. It's not at all obvious to most of the world's web designers and content creators that a static site should be TLS'd until it's framed (heh) in this manner. The fact that you asked brings about a massive educational moment. Anyway, consider switching hosts. :)
- deleted 10y ago[deleted]
- cmdrfred 10y agoMay I add an example. Let's say you are a drug company and you offer a number of different drugs. With TLS I only know that you are interested in a drug that company produces or the company itself, without it I know you or someone you care about has erectile dysfunction.
- spand 10y agoNo that is not all an attacker could know. TLS does not provide confidentiality of the number of bytes transmitted. So in your example an attacker would only have to crawl the public website and find the pages matching in size to the ones you have been browsing.
- 10y ago
- riobard 10y agoHere's why: Many ISPs hijack HTTP connections and inject ads and tracking JS into the page. If you don't use HTTPS, your page is screwed. The Internet is not a safe place. We should aim for HTTPS EVERYWHERE.
- RadioactiveMan 10y agoThis is a really good point. Usually we talk about protecting against a third party, but the far more ordinary use case is protecting against the adversary right on the other side of your router.
- snug 10y ago> Many ISPs I think that's a bit sensationalist.
- mrkurt 10y agoIt's not, it happens at a ton of coffee shops, on airplanes, etc, etc. Probably not ISPs you buy home internet from, but there are a lot.
- STRML 10y agoVerizon, Comcast, and Rogers have done it, that we know of. In North America that's a very large proportion of traffic.
- afandian 10y agoVodafone in the UK did this to me.
- chatmasta 10y agoVodafone is the worst. Although it's really the U.K. surveillance state that is the problem. When I popped my SIM into my iPhone it forced me to download a configuration profile with a self-signed Vodafone cert, which means they can mitm any connection. I think this is required by the government so they can block adult websites by default? (I've also seen torrent websites also fail silently with misleading "server not found" errors) I haven't looked into if they're doing the filtering via DNS or mitm, but I avoid the censorship by connecting to a vpn.
- Gurrewe 10y agoIf you have a marketing webpage, you might have a link to signup or login pages. If you can hijack the index page you'll also be able to hijack the links.
- mikeash 10y agoEven if you don't have signup or login pages, a MITM attacker can add them. Or they could add a "buy now!" link with a convenient entry form for the user's bank details. The relevant question isn't what your page has that's so important, but rather what an attacker could make it have that would cause trouble.
- mrkurt 10y agoMost of the answers you're getting aren't all that big of deal for your site. You still might want https though. You should think about https for sites like yours the way you think about vaccines. SSL everywhere makes everyone safer, even though it doesn't have a tremendous impact on your own site. Also, shameless plug, if you want really easy SSL you can use our new startup: https://fly.io https://fly.io. I'm not sure what country you're in, but we have a bunch of servers all over to help make it fast. :)
- deallocator 10y agoBut of nitpicking, but on mobile the balloon is cut off a bit at the top :)
- mrkurt 10y agoHuh. Which device/browser? It's such a pretty balloon, I'd hate to lose a piece of it. You can email me if you want to avoid cluttering HN: mrkurt at gmail.
- ReverseCold 10y ago500
- mrkurt 10y agoWell that's embarrassing. :/
- rocqua 10y ago2 reasons. The first is practical: integrity. Https guarantees the site your visitors see is the site you sent them. The second is more moral. Making https the default means more and more of the web will be encrypted and authenticated. This is a good thing.
- dalore 10y agoWhy use ssh over telnet?