-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Blocking all LAN #508
Comments
@funilrys which input source is this coming in from? We need to create a permanent whitelist for all private networking ranges to avoid this creeping back in every now and again |
|
Also: Introduction of the tests in order to avoid such isssues in the future
Because of #508 and its fix Ultimate-Hosts-Blacklist/whitelist@57f308e. New data will be available in about 15 minutes.
Service Note: Had to restart the build because the wrong version of the whitelisting tool was installed. It is now the correct one. New data will be available in the next 10-15 minutes. |
@mitchellkrogza firehol1 |
I will no longer report this |
Thanks @unbranched, no need to. Tests are written and will be improved with the time as you can see at Ultimate-Hosts-Blacklist/whitelist@57f308e#diff-91096435e85fc2eb752d068ef2758f5d. It will now be checked before a release of a new version of the whitelisting tool. Cheers, |
Closing. Not present anymore at https://raw.githubusercontent.com/mitchellkrogza/Ultimate.Hosts.Blacklist/master/superhosts.deny/superhosts7.deny:
|
Just a side note @mitchellkrogza, Since Ultimate-Hosts-Blacklist/whitelist@9c251b7, all reserved IPv4 are now whitelisted by the whitelisting tool. Of course, tests shipped along with it to avoid future issues. Cheers, |
It's included again
ALL: 192.168.0.0/16
The text was updated successfully, but these errors were encountered: