[bug] Wildcard TLDs in SimplePolicy MRF does not work #431

New Issue

Closed

opened 2023-01-09 02:23:11 +00:00 by Ghost · 2 comments

Ghost commented

2023-01-09 02:23:11 +00:00

Few instance admins, including my own instance, have reported that wildcard TLDs in SimplePolicy MRF do not work.

Say an instance has multiple domains with the same name but different TLD to block evade (e.g. badinstance.cc, badinstance.com, badinstance.xyz)

Instead of adding all 3 of those domains individually, we'd like to be able to just set badinstance.* so not only will it block all subdomains, it will block all TLDs. However, this doesn't seem to work.

Few instance admins, including my own instance, have reported that wildcard TLDs in SimplePolicy MRF do not work. Say an instance has multiple domains with the same name but different TLD to block evade (e.g. badinstance.cc, badinstance.com, badinstance.xyz) Instead of adding all 3 of those domains individually, we'd like to be able to just set `badinstance.*` so not only will it block all subdomains, it will block all TLDs. However, this doesn't seem to work.

floatingghost commented

2023-01-09 02:25:29 +00:00

Owner

clarifiation: wildcard blocks of the standard form do work, i.e *.example.com

however reverse-wildcards are not supported

clarifiation: wildcard blocks of the standard form _do_ work, i.e `*.example.com` however reverse-wildcards are not supported

Ghost commented

2023-01-09 02:36:57 +00:00

Author

Is this doable? Some of us have been under the wrong impression about how this works and now we need to adjust our MRFs to block a bunch of individual known block-evading domains because we can't just wildcard block a TLD.