Given that the Jargon File / Hacker’s Dictionary predates https by at least 20 years and is not remotely sensitive information, I don’t think it’s a problem.
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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
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
Recommend also the seminal TMRC dictionary for several terms absent here, plus some memorably elegant definitions:
Kludge: A crock that works.
Crock: A kludge that doesn’t work.
Same again true of Peter Samson’s original 1959 and 1960 editions.
Hmmm, hosting a hacker post without an https url… 🤨
Given that the Jargon File / Hacker’s Dictionary predates https by at least 20 years and is not remotely sensitive information, I don’t think it’s a problem.
https://en.wikipedia.org/wiki/Jargon_file
http://www.catb.org/~esr/jargon/
P.S. This entry in particular might be informative:
http://www.hackersdictionary.com/html/entry/hacker.html
Maybe I’m wrong, but using http could create a MITM vulnerability.
And for me this issue is my browser is setup to block http URLs. It’s just not a good look.
You are. The only way it “creates a MITM vuln” is if you’re entering sensitive information into the site, which you’re not.
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:
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
get with the times, https is not 1337