Say (an encrypted) hello to a more private internet. - eviltoast
  • Danny M@lemmy.escapebigtech.info
    link
    fedilink
    arrow-up
    13
    ·
    1 year ago

    somebody wiresharking your traffic can see the domain name you’re contacting even if you use https; this solves that.

    reverse DNS lookup does exist, but it’s not always accurate, especially when multiple websites are hosted on the same server (which is more common than you think)

    • JCpac@lemmy.today
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Is it because of the “Host” HTTP header? I always thought it was optional, since the IP address and port were handled by the network and transport layers respectively. Turns out it’s required to resolve between different virtual hosts in the same server. Today I Remembered (TIR?) that virtual hosts are a thing…

      Is there anything else that might indicate the domain name in the handshake connection?

      • Domi@lemmy.secnd.me
        link
        fedilink
        arrow-up
        8
        ·
        1 year ago

        Is there anything else that might indicate the domain name in the handshake connection?

        The SNI (Server Name Indication) happens before any HTTP communication and is done in plain text. It is needed because a single web server might host multiple websites, since each of them has their own certificate it needs to know which one to serve you.

        With the new proposal that SNI is now encrypted. It makes the difference between anyone listening in being able to tell “you visited lemmy.world” and “you visited something behind Cloudflare”.