Programming

17374 readers

156 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

the hacker's dictionary (www.hackersdictionary.com)

submitted 1 year ago by sizeoftheuniverse@programming.dev to c/programming@programming.dev

7 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Hexarei@programming.dev 5 points 1 year ago (1 children)

Maybe I'm wrong,

You are. The only way it "creates a MITM vuln" is if you're entering sensitive information into the site, which you're not.

[–] noli@programming.dev 2 points 1 year ago

It does create a MITM vulnerability, the question is just whether it matters or not. With HTTPS a third party will only know which url you're accessing. With HTTP they can see exactly what data is transferred and can modify that data at will.

So adding HTTPS here accomplishes:

hiding which exact page of the hacker's dictionary you're accessing
hiding the exact contents of the page
ensuring that this page doesn't get modified in transit

None of these are really an issue, so using http in this situation is fine. In general though, I'd consider not having HTTPS as a bug for most sites, unless you're extremely resource constrained on either side of the connection and you think carefully about the security and privacy implications