Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Domain lgse.com in AdguardDNS.txt but not in AdGuardSDNSFilter repo lists #214

Closed
AndisGrossteins opened this issue Nov 3, 2024 · 1 comment

Comments

@AndisGrossteins
Copy link

I just stumbled upon a blocked domain in you AdguardDNS.txt which I can't seem to find in the rules.txt of AdguardTeam/AdGuardSDNSFilter repo. Although it's in the filter.txt version linked from their README.md which I assume you're parsing to generate plain hosts list.

I found the domain linked in a composer.json file from the slimphp/Slim-Skeleton repo for one of the Slim framework authors – Pierre Berube (@l0gicgate).

For some reason the web server has misconfigured TLS cert (net::ERR_CERT_COMMON_NAME_INVALID – plain lgse.com has cert for static.lgse.com) but that wouldn't be a good reason to put it on a blocklist. However, I'll leave that to Pierre to sort out.

@WaLLy3K
Copy link
Owner

WaLLy3K commented Jan 12, 2025

https://v.firebog.net/hosts/AdguardDNS.txt is parsed from https://filters.adtidy.org/extension/chromium/filters/15.txt where ||lgse.com^ is found on line 15427.

https://v.firebog.net/hosts/Easylist.txt is parsed from https://easylist-downloads.adblockplus.org/easylist.txt where ||lgse.com^ is found on line 29872.

I know that that the maintainers for those lists will say that their lists aren't meant to be used in a HOSTS style blocklist, however I'm certain that I'm interpreting this correctly. If there is something to fix with how I parse these lists though, I absolutely will fix it up if I'm aware of it. 🙂

A whitelist request should be submitted here:
https://github.com/AdguardTeam/AdGuardSDNSFilter/issues
https://github.com/easylist/easylist#list-issues

@WaLLy3K WaLLy3K closed this as completed Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants