Any chance of adding support for this open-source blocklist project?
-
https://github.com/crazy-max/WindowsSpyBlocker
It's a project to detect and block Windows telemetry privacy breaches, and optionally others, which automatically detects in-use privacy breaching IPs and domains, updates its IP list, and makes it available free in a number of formats for various IP block platforms.
It looks popular, well supported, and ideal for a pfBlockerNG option or list. I'm in chaotic busy mode or I'd do a PR myself, but I just won't have spare capacity for ages.
Any chance of it being added anyway, by someone who likes the idea :)
-
Hi Stilez,
They already have feeds for the various Windows telemetry here:
https://github.com/crazy-max/WindowsSpyBlocker/tree/master/data/firewallThey are also formatted correctly for DNSBL to use as-is…
Not sure if you are talking about adding functionality to find the IPs automatically? Which is probably a lot more involved? and maybe unnecessary if they already have provided a regularly updated list of feeds?
which automatically detects in-use privacy breaching IPs and domains, updates its IP list, and makes it available free in a number of formats for various IP block platforms
-
I mean, a "one click option" to automatically import and use (and periodically update) the anti-telemetry IP lists which this project collates.
-
The next version of the pkg will have a Feeds Management tab which will allow predefined Alias/Groups to be easily imported into the configuration.
I have no issue in adding these to the new Feeds Management Tab, but I haven't tested these feeds myself, so it would be great if others can chime in on how well these feeds are working before I add them.
Windows telemetry:
https://github.com/crazy-max/WindowsSpyBlocker/tree/master/data/firewall -
I have had a look at this feed a while back. It is pretty poor IMHO and I wouldn’t recommend it, if they included the suggested changes it would be even worse. One of the worst things is that it just arbitrarily blocks random chunks of Microsoft services (including ones you may have whitelisted) by blocking some of the intermediate CNAME domains (like a-msedge.net) Not to mention that some of them are not tracking servers but provide other services (like the weather for the live tile.)
Quite a lot of the lists blocking Microsoft tracking are similarly bad, I have to assume that they don’t test very well if at all. Recently I’ve had to pull the Phishtank feed (supposedly a list of phishing domains), the last straw was when they added login.live.com (which is quite a useful one if you actually use pretty much any Microsoft services at all!)
I’m not bad at tracking down the DNS responses to find the issues but for a relative novice to find a whitelisted domain suddenly blocked and showing as whitelisted in pfB it would be infuriating.
-
I have had a look at this feed a while back. It is pretty poor IMHO and I wouldn’t recommend it, if they included the suggested changes it would be even worse. One of the worst things is that it just arbitrarily blocks random chunks of Microsoft services (including ones you may have whitelisted) by blocking some of the intermediate CNAME domains (like a-msedge.net) Not to mention that some of them are not tracking servers but provide other services (like the weather for the live tile.)
Quite a lot of the lists blocking Microsoft tracking are similarly bad, I have to assume that they don’t test very well if at all. Recently I’ve had to pull the Phishtank feed (supposedly a list of phishing domains), the last straw was when they added login.live.com (which is quite a useful one if you actually use pretty much any Microsoft services at all!)
I’m not bad at tracking down the DNS responses to find the issues but for a relative novice to find a whitelisted domain suddenly blocked and showing as whitelisted in pfB it would be infuriating.
I have always been hesitant to recommend these types of Feeds… So unless there is more feedback, I will just hold until more people chime in....