Daily reminder that sites “protected” by cloudflare are effectively MITM attacks. HTTPS is now even more worthless. Cloudflare can see everything. this is a known fact and not a theory.

And if you think Cloudflare aren’t being tapped by the NSA, you’re sadly sadly naive.

All the “privacy respecting” sites use it too. So remember, as soon as you see that cloudflare portal page, you can assume that everything you plug into the site is property of NSA Inc. Trust no one, and do not trust code being served to you over the web if it comes through CF, there is no way to know what they’ve modified.

Edit: good info link below https://serverfault.com/questions/662946/does-cloudflare-know-the-decrypted-content-when-using-a-https-connection

  • @[email protected]
    4•6 months ago

    Is this also true about the cloudflare DNS over HTTPS option that Firefox provides in the privacy settings? If yes, then would it help if I changed the setting from ‘Cloudflare’ to ‘NextDNS’?

    • edric
      6•6 months ago

      I personally use Mullvad on my FF DNS settings.

    • voxel
      4•6 months ago

      that’s just dns tho
      but yeah, obviously your dns provider can see the dns requests (aka domain names) you’re making, that’s the whole point of dns server

    • @[email protected]
      2•6 months ago

      I use quad9 with DNS over TLS systemwide with openbsd unwind

      unwind.conf config

      forwarder { 9.9.9.9 port 853 DoT 149.112.112.112 port 853 DoT }
preference { DoT }

      firefox’s use of cloudflare for DoH is irresponsible, and possibly worse than just sending your DNS queries to your ISP’s default servers. It would be in line with Mozilla’s other practices though.

    • asudox
      1•6 months ago

      I’d suggest you use the DNS mullvad provides.