“Concerns over DNS Blocking” by Vinton Cerf

  • MrMonkey@lemm.ee
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    How? I don’t see what could find dns-over-https in the middle of other https traffic?

    • Brkdncr@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      there is a lot more to modern firewall app detection than ports. My Palo Alto has a specific category to detect and block dns over https.

        • Brkdncr@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          For rather cheap I can see what traffic is suspicious. If you throw more resources at the problem and scale up it becomes simple to see traffic that looks like dns over https without having to decrypt it. Indicators such as size, frequency, consistent traffic going from your host to your DoH provider and then traffic going to other parts of the internet….these patterns become easy to establish. Once you have a good idea that a host on the internet is a DoH provider you can drop it into that category and block it.

    • Hot Saucerman
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      Port number is pretty indicative of DNS traffic, if we’re talking IPv4.