“Concerns over DNS Blocking” by Vinton Cerf

  • jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    As much as I dislike wasteful cryptography, this seems like an really good use case for cryptographically signed and owned names. Kind of like ENS domain names.

    That way no single third party you can remove you from the internet effectively

  • Hot Saucerman@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    French people really like to protest, so maybe we can teach them all to set up their own DNS resolvers with Raspberry Pis?

    It would be a really, really difficult law to police if individuals were all managing their own DNS resolvers.

    • z3bra@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Sure we do, but you cannot expect everyone to simply run their own DNS and call it a day.

      The vast majority of people don’t even know that DNS even exist, let alone that your ISP can monitor/alter your traffic through it.

      • Hot Saucerman@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I’ll admit, it’s a much less “exciting” way to protest than flipping cop cars and starting fires.

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

    PiHole with upstream dns-over-tls or dns-over-https.

    Anybody who wants to can get around DNS blocks. Sure it’ll stop Aunt Sally, but anyone who cares will get around it. It’s a really dumb way of doing things.

      • MrMonkey@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        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
          1
          ·
          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.