• bia@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    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.

    • Hexarei@programming.dev
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

      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
        link
        fedilink
        arrow-up
        2
        ·
        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