Document reasoning to block DNS to 127.0.0.1

Re:Document reasoning to block DNS to 127.0.0.1 by oefrha on Tuesday June 20, 2023 @12:25AM (#36399699)

Not a fan of EasyPrivacy. It seems to be run by trigger happy people with pretty limited understanding of the web.

They once blocked workers.dev (Cloudflare Workers) wholesale[1], resulting in a huge flood of issue reports for a few FOSS services of mine. Guess they've never heard of public suffixes.

This one appears to be someone reading about DNS rebinding attack somewhere, then pulling the trigger without understanding it. Or maybe I even overestimated them, DNS rebinding only came up as a justification very deep into the discussion.

To make matters worse, clients using these block lists have update frequencies all over the place, so you can never be sure when your stuff gets unborked for all your users even after they revert changes like this.

[1] https://github.com/easylist/easylist/commit/e4b0216

[ Parent | on HN ]

Re:Document reasoning to block DNS to 127.0.0.1 by oefrha on Tuesday June 20, 2023 @02:33AM (#36400459)

Edit: Actually, DNS rebinding was brought up by the issue reporter, all that the committer presented was some handwavy "give me a reason I shouldn't block this"... How about checking the sites you blocked for a reason.

[ Parent | on HN ]