itman 1,659 Posted March 17 Share Posted March 17 This also is very informative and might be what is going on here: https://www.securityweek.com/cloudflare-users-exposed-to-attacks-launched-from-within-cloudflare-researchers/ . Quote Link to comment Share on other sites More sharing options...
itman 1,659 Posted March 23 Share Posted March 23 (edited) Another issue with Firefox DNS over HTTPS or not if you're using a VPN. It will leak your ISP DNS servers: https://connect.mozilla.org/t5/discussions/firefox-has-dns-leak-security-issue/td-p/50582 . Edited March 23 by itman Quote Link to comment Share on other sites More sharing options...
itman 1,659 Posted March 23 Share Posted March 23 (edited) Well, I'll be damned. I got Firefox to detect https://crackingpatching.com/2017/03/avast-pro-antivirus-internet-security-premier-17-2-3419-0-keys.html with DNS over HTTPS enabled. The problem turns out to be HTTP/3 ; i.e. QUIC, as discussed in the other recent thread on this issue. Set network.http.http3.enable setting via about:config option to false and Eset now detects every time. I will also add that disabling HTTP/3 in Firefox does not disable it as far as Firefox DNS over HTTPS server processing goes. Using Cloudflare check: https://www.cloudflare.com/ssl/encrypted-sni/ shows HTTP/3 is enabled. Edited March 23 by itman Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.