Here's Why Your Static Website Needs HTTPS
Troy HuntRecommended by 2 HN commenters across 2 months, 2020–2023
talk · general · evergreen · 2020–2023 on HN
Troy Hunt argues that even static, non-secret websites need HTTPS, demonstrating attacks such as injected content and China's Great Cannon. It accompanies his blog post of the same name.
Cited as a must-watch persuasive case for HTTPS everywhere.
Up next
11 mo on HNBehind the Scenes of iOS Security
Black Hat
Recommended 9× on HN · 2016–2026
11 mo on HNWhy Electronic Voting Is Still A Bad Idea
Tom Scott
Recommended 11× on HN · 2020–2026
10 mo on HNUSENIX Security '18-Q: Why Do Keynote Speakers Keep Suggesting That Improving Security Is Possible?
USENIX
Recommended 10× on HN · 2018–2026
10 mo on HNDefcon 18 Changing threats to privacy Moxie Marlinspike Part
killab66661
Recommended 6× on HN · 2012–2019
9 mo on HN28c3: The Science of Insecurity
28c3
Recommended 9× on HN · 2012–2024
8 mo on HNDEF CON 25 - John Sotos - Genetic Diseases to Guide Digital Hacks of the Human Genome
DEFCONConference
Recommended 11× on HN · 2017–2023
7 mo on HNElevator Hacking: From the Pit to the Penthouse
DeviantOllam
Recommended 9× on HN · 2014–2026
7 mo on HNCompiling C to printable x86, to make an executable research paper
suckerpinch
Recommended 8× on HN · 2018–2023
7 mo on HNBreak Me00 The MoVfuscator Turning mov into a soul crushing RE nightmare Christopher Domas
Adrian Crenshaw
Recommended 6× on HN · 2017–2026
7 mo on HNBlackHat USA 2011: SSL And The Future Of Authenticity
Christiaan008
Recommended 9× on HN · 2011–2017
7 mo on HN27C3: Adventures in analyzing Stuxnet (Bruce Dang from Microsoft)
basti0007
Recommended 8× on HN · 2011–2024
7 mo on HNFrank Abagnale | Catch Me If You Can | Talks at Google
Talks at Google
Recommended 8× on HN · 2018–2023
3 comments from Hacker News
This was the article that convinced me to be HTTPS everywhere (well maybe in 99.99% cases if not everywhere). The linked video is a must watch to those who still doubt HTTPS[0]. The mention of China's Great Cannon was particularly eye-opening[1]. 0. ▶ this video 1. link
link The whole video is great, but particularly this: ▶ this video link There are a lot of arguments about why, even non-secret data connection need encryption. The first and most obvious is that not doing so immediately puts a target on the encrypted data. By no means an expert but to me it seems like an oversight not to.
The reason I'd advocate in more public settings is that things ought to be secure-by-default, and that adopting security only upon realizing its necessity is a hazard-prone policy that constantly backfires. But for a specific example of something that could go wrong: someone could inject malicious content into a non-secure page. The original content might be plain-text, but a man-in-the-middle can still inject whatever they like regardless. As a common example of a simple attack: an attacker could man-in-the-middle people who connect to a nearby wireless network. Notes: 1. There're a bunch of ways that an attacker could get people to connect to their network. Examples: spoofing a legitimate network; setting up a password-less network; putting up a poster falsely advertising the SSID/pass to a network that falsely purports itself to be official; they're an actual employee of the establishment and just compromise the legitimate network; they're a remote-hacker who's exploited a vulnerability in the router. 2. The attacker could do lots of random stuff. Examples: they could inject malicious code; they could inject misinformation to facilitate scamming someone; they could insert ads; steal CPU-time/electricity for crypto-mining; they could just put gross porno on everyone's phone in a restaurant as a troll. Or something else. Or multiple things. 3. The original site being just plain-text doesn't really matter; the attacker can replace the entire thing without even contacting the