News for hackers. Stuff that matters.
Re:Website is hosted on ESP32 ($3 chip) by arthurcolle on Sunday November 05, 2023 @04:55PM (#38156050)
How can you reliably know that you're not being MITM without HSTS?
Re:Website is hosted on ESP32 ($3 chip) by anigbrowl on Sunday November 05, 2023 @05:21PM (#38156262)
Not my problem if I am just serving a static page.

For a commercial service or if I was handling people's credentials I'd use something more robust.

Re:Website is hosted on ESP32 ($3 chip) by xboxnolifes on Sunday November 05, 2023 @06:23PM (#38156814)
It is your problem if you're interested in making sure people are actually getting your static page.
Re:Website is hosted on ESP32 ($3 chip) by ZeroSolstice on Sunday November 05, 2023 @10:04PM (#38158317)
I'm sure there is some nuance to what someones static site is serving but someones blog doesn't need to be HTTPS. If they are offering downloads you can provide checksums or verify their data through other sources or contacting them out-of-band.

Anything that needs some form of validation from any site should be verifiable in multiple ways. Just because they have HTTPS doesn't mean the provided information or data is automatically correct.

Re:Website is hosted on ESP32 ($3 chip) by xboxnolifes on Monday November 06, 2023 @06:39PM (#38170891)
The entire website can be rewritten by a MITM without https. Checksum or no checksum is not helpful.
Re:Website is hosted on ESP32 ($3 chip) by ZeroSolstice on Monday November 06, 2023 @08:48PM (#38172109)
The attack you are suggesting is not commensurate to the types of blogs and information that _need_ HTTPS.

If you are operating at a level where your personal blog can have all possible transit paths compromised by a third-party such that they are hosting some or all resources that you provide for download, modifying them and producing new checksums then you have bigger problems than a blog that doesn't have HTTPS. You would also at that point consider using someone else's platform that will absorb or actively be motivated to thwart these exact scenarios. Not to say that always works out[1].

Additionally your concern of checksums being compromised can easily be thwarted by hosting packages on github, gitlab, bitbucket, pastebin, or a google groups mailing list. All of which still don't require your blog to have HTTPS. You don't have to manage getting your own certificate, paying for yearly renewals or setup any auto-90-day let's encrypt auto-bot.

Great grandma's cookbook recipes on a blog don't need HTTPS.

[1] https://www.zdnet.com/article/krebs-on-security-booted-off-a...

Re:Website is hosted on ESP32 ($3 chip) by mikewarot on Sunday November 05, 2023 @04:58PM (#38156064)
How can you know you're not with HSTS? The whole centralized security system is suspicious in terms of failure points.
Re:Website is hosted on ESP32 ($3 chip) by woodruffw on Sunday November 05, 2023 @05:07PM (#38156130)
The Web PKI is hierarchical, but it isn't particularly centralized (other than Let's Encrypt increasingly eating everyone else's lunch, which is probably a good thing).

But in terms of actual failure points: if you're initiating a connection over HTTPS, then the only way an attacker can MITM you is by convincing a CA to incorrectly issue them a certificate for that domain. That's why Chrome and Safari monitor certificate transparency logs, and why website operations should also generally monitor the logs (to look for evidence of misissuance on their own domains).