• Rikudou_Sage@lemmings.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    It is kinda big, previously you had to send the host unencrypted to support SNI which in turn was needed to support https for multiple sites per one IP address, which was needed because we lack IP addresses. So there were basically two options: compromise privacy a tiny bit (by sending host unencrypted), or make it impossible for most websites to have any privacy at all (by making it impossible to have a https certificate).

    Now you can have the best of both worlds. Granted, you need to have DoH (which still isn’t the default on most systems AFAIK), but it’s still a step in the right direction.

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

    I don’t get it… How does this protect anything? If we want our packets to reach a web server, we need to write the server’s IP address on them. If a snooper has the IP, can’t they just lookup the domain name from a DNS server? Or is that not a service DNS provides?

    If the IP address is encrypted, how will the routers know where to send the packets? Only solution I can think of would be onion routing… Am I wrong??

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

      An IP address is no longer associated with just one website/domain name. There could be thousands of websites running on a single IP address.

      As is, anyone can currently look at your encrypted traffic and see in plain text which site you’re surfing to. So this proposal is long overdue.

  • Boring@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    While this is good for survielience circumventing… It is looking like the beginning of the end of DNS filtering and the popularization of encrypted telemetry.