Replies: 1 comment
-
|
Hey @jedisct1, what do you think of this? Is it something that can be improved? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using generate-domains-blocklist.py to merge some lists and I found an issue using domains-allowlist.txt file.
We have a legit domain, in this case
example.com. and there are few bad subdomains, likead.example.com,malware.example.com,tracker.example.comand so on ... all of them blocked by a source merged during the process.Now I add a new source that accidentaly block
example.com, well, I addexample.comtodomains-allowlist.txtfile and I run the script.Result:
The
listdoesn't containexample.com,ad.example.com,malware.example.com,tracker.example.com,...Expected result:
The
listshould containad.example.com,malware.example.com,tracker.example.com,...but notexample.comNot a solution:
I can use
allowed-names.txtand add=example.comin there. So we start to generate duplicates rules:example.comfor the block and=example.comfor the unlock.But the important thing is that the script remove the subdomains because
example.comin contained in one of the source merged and thenexample.comis removed because is contained indomains-allowlist.txtfile and I lose the possibility to block all of them.Solution:
Implement
=support indomains-allowlist.txtfile and during the process excludeexample.comdomain only without excludingad.example.com,malware.example.com,tracker.example.com,...anymore.Beta Was this translation helpful? Give feedback.
All reactions