Here's Why Your Static Website Needs HTTPS
Troy Hunt2 HN recommenders · recommended in 2 months, 2020-2023
30K views · 8 years ago · talk · evergreen
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.
20:21Humans can't read URLs. How can we fix it? - HTTP 203
Chrome for Developers
59K views • 6 years ago
46:22DEF CON 19 - Moxie Marlinspike - SSL And The Future Of Authenticity
DEFCONConference
11K views • 13 years ago
1:09:16Defeating Ssl Using Sslstrip (Marlinspike Blackhat)
TheSecurityTube
61K views • 14 years ago
33:24Brian Warner - Magic Wormhole- Simple Secure File Transfer - PyCon 2016.mp4
PyCon 2016
44K views • 10 years ago
25:14Rick Reacts to Lightning (Again) and brings up a previously undiscussed flaw
We Are All Satoshi
14K views • 8 years ago
45:37Beyond Passwords: Secure Authentication with Mozilla Persona
Next Day Video
3K views • 13 years ago
46:04DEF CON 26 - Christopher Domas - GOD MODE UNLOCKED Hardware Backdoors in redacted x86
DEFCONConference
86K views • 8 years ago
31:38Cory Benfield - Building Protocol Libraries The Right Way - PyCon 2016
PyCon 2016
15K views • 10 years ago
7:26This Video Is Sponsored By ███ VPN
Tom Scott
5.9M views • 7 years ago
25:37CUFP 2013: Julien Verlaguet, Facebook: Analyzing PHP statically
CUFP 2013
5K views • 13 years ago
1:01:39NYCBSDCon 2014: Serving one-third of the Internet via FreeBSD
BSDTV
14K views • 12 years ago
1:00:57Tobias Engel: SS7: Locate. Track. Manipulate.
media.ccc.de
84K views • 11 years ago
37:37RailsConf 2016 - Turbolinks 5: I Can’t Believe It’s Not Native! by Sam Stephenson
Confreaks
61K views • 10 years ago
45:05Servo Architecture: Safety and Performance
linux conf au 2017 - Hobart, Australia
12K views • 9 years ago
45:14DEF CON 19 - Artem Dinaburg - Bit-squatting: DNS Hijacking Without Exploitation
DEFCONConference
4K views • 13 years ago
49:43ZFS Native Encryption by Tom Caputi
OpenZFS
14K views • 10 years ago
48:02BlackHat USA 2011: SSL And The Future Of Authenticity
Christiaan008
95K views • 15 years ago
29:47The Truth about Rust/WebAssembly Performance
Greg Johnston
218K views • 3 years ago
24:20Satoshi Has No Clothes: Failures in On-Chain Privacy by Ian Miers (Devcon4)
Ethereum Foundation
5K views • 7 years ago
12:24Elliptic Curve Back Door - Computerphile
Computerphile
554K views • 8 years ago
3 comments from Hacker News
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
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