News for hackers. Stuff that matters.
Re:Why Static Websites Need HTTPS by dragonwriter on Tuesday August 28, 2018 @11:42AM (#17859670)
> A MITM attack on a static site is definitely possible, maybe even easy, but I'm not going to worry about it unless I have something important to protect.

HTTPS doesn't protect the content of your site from being stolen, it protects your users from hostile third-party content masquerading as yours.

Re:Why Static Websites Need HTTPS by mrfredward on Tuesday August 28, 2018 @12:44PM (#17860350)
>it protects your users from hostile third-party content masquerading as yours

Exactly. What does anyone lose if my anonymous untrusted blog does something untrustworthy for that one reader who has an infected router?

Should I encrypt messages I write on post cards, because I'm afraid a disgruntled postal worker will write "you suck" on the bottom? The worst case scenario here is temporary vandalism.

Re:Why Static Websites Need HTTPS by mrob on Tuesday August 28, 2018 @01:40PM (#17860921)
The same argument applies to littering. It's only going to harm strangers, and you're unlikely to get caught, so strictly from a cost-benefit perspective it seems like a good idea. But if everyone makes that "rational" decision then we all lose.
Re:Why Static Websites Need HTTPS by 3pt14159 on Tuesday August 28, 2018 @01:57PM (#17861113)
The problem is that as a community we want to move to where no traffic is unencrypted so the MITM don't have to be trusted. If your static site wants an exception then your static site is going to be where I get hit.
Re:Why Static Websites Need HTTPS by lostapathy on Tuesday August 28, 2018 @01:34PM (#17860845)
No, the worst case scenario is that the user gets compromised/infected and becomes part of a botnet that attacks the rest of us.
Re:Why Static Websites Need HTTPS by yardstick on Tuesday August 28, 2018 @02:37PM (#17861556)
> HTTPS doesn't protect the content of your site from being stolen, it protects your users from hostile third-party content masquerading as yours.

Hostile third party content is only hostile because the client used to access the content does not take client security seriously.

Food for thought: As an end user consumer visiting random, benign websites, I want my browser to be protecting me against hostiles, rather than relying on website operators to do that for me. Just like I run antivirus on my machines instead of relying on everyone else to run it.

Re:Why Static Websites Need HTTPS by chopin on Wednesday August 29, 2018 @03:55AM (#17866518)
Just make it so that your browser doesn't render any http delivered content. Problem solved. From a client point of view that's the only protection you can do. A MITM over http is undetectable for you. With current OSes and hardware there is no sandboxing which will protect you under all circumstances.

If you do this, site providers are forced to switch to https anyway.

Re:Why Static Websites Need HTTPS by dragonwriter on Wednesday August 29, 2018 @09:45AM (#17868155)
> If you do this, site providers are forced to switch to https anyway.

No, if everyone does this, providers are forced to switch. If you do it, it just means you're cut off from some portion of the web.