-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
hosts file has line with unexpected content #1004
Comments
Hello! Thank you for opening your first issue in this repo. It’s people like you who make these host files better! |
Thank you Alex @alexsannikov. Ping Tomasz @FadeMind. These lines (lines 2028 to 2031) appear to be a problem.... |
I'm wondering if we should actively filter lines like this. Thoughts?
Edit: this stackoverflow thread has an interesting and promising-looking regex.
|
Ping @azet12 @krystian3w |
This are pages with fake flash player. Works on IP only.
this should down so I can remove 2 problematic rules. IP may are pared with one server by https://github.com/emnh/homepage from Norway. |
StevenBlack/hosts#1004 za jakieś 20 dni się wywali pozostałe dwa, bo już nie mam w historii adresów do nich.
Thanks @krystian3w. An IP address is NOT a valid host name. See RFC 952. The status of RFC 952 is,
|
OK added on uBo list names "directory" used for scam and problematic websites without host name gone from KAD HOSTS. |
Thank you @krystian3w! |
This is fixed in release 2.4.12. Thank you, everybody. Closing. |
Sorry guys, I've opened new Issue #1006 to point to the additional IP address in another list. |
Hello,
I am using this repo as a source to build more "intellectual" filters lists for AdGuard Home.
I use some scripts to collapse the content and apply using regexp, as AdGuard Home supports it.
The following line which I found in "hosts" file (admalware) doesn't make sense and breaking my filters, leaving "www" only, which prohibit using any domain name starting from "www".
user@linux:/tmp $ cat hosts | grep "0.0.0.0 www "
0.0.0.0 www #.104.248.94.172
user@linux:/tmp $
The text was updated successfully, but these errors were encountered: