search

bongochong / CombinedPrivacyBlockLists

Ad-blocking hosts files, IP block lists, PAC filters, ABP / uBO / ADG subscriptions, and a whole lot more. All merged from multiple reputable sources, combined with my own research. Also, script-based utilities to help you create such things yourself. Updated at least once every two weeks, often more frequently.
Other
234 stars 26 forks source link

[RESOLVED] CNAMEs for skyapi.onedrive.live.com break OneDrive #19

Closed p1r473 closed 3 years ago

p1r473 commented 3 years ago

image i-am3p-cor001.api.p001.1drv.com i-am3p-cor002.api.p001.1drv.com i-am3p-cor003.api.p001.1drv.com i-am3p-cor004.api.p001.1drv.com i-am3p-cor005.api.p001.1drv.com i-bl6p-cor001.api.p001.1drv.com i-bl6p-cor002.api.p001.1drv.com i-bn3p-cor001.api.p001.1drv.com i-bn3p-cor090.api.p001.1drv.com i-by3p-cor001.api.p001.1drv.com i-by3p-cor002.api.p001.1drv.com i-ch1-cor001.api.p001.1drv.com i-ch1-cor002.api.p001.1drv.com i-db3p-cor001.api.p001.1drv.com i-db3p-cor002.api.p001.1drv.com i-db3p-cor003.api.p001.1drv.com i-db3p-cor004.api.p001.1drv.com i-db3p-cor005.api.p001.1drv.com i-sn2-cor001.api.p001.1drv.com i-sn2-cor002.api.p001.1drv.com i-sn3p-cor001.api.p001.1drv.com i-sn3p-cor002.api.p001.1drv.com ch1-cor001.api.p001.1drv.com ch1-cor002.api.p001.1drv.com bn2b-cor001.api.p001.1drv.com bn2b-cor002.api.p001.1drv.com bn2b-cor003.api.p001.1drv.com bn2b-cor004.api.p001.1drv.com bn2wns1.wns.windows.com bn3p-cor001.api.p001.1drv.com bn3sch020010558.wns.windows.com bn3sch020010560.wns.windows.com bn3sch020010618.wns.windows.com bn3sch020010629.wns.windows.com bn3sch020010631.wns.windows.com bn3sch020010635.wns.windows.com bn3sch020010636.wns.windows.com bn3sch020010650.wns.windows.com bn3sch020011727.wns.windows.com bn3sch020012850.wns.windows.com bn3sch020020322.wns.windows.com bn3sch020020749.wns.windows.com bn3sch020022328.wns.windows.com bn3sch020022335.wns.windows.com bn3sch020022361.wns.windows.com bn4sch101120814.wns.windows.com bn4sch101120818.wns.windows.com bn4sch101120911.wns.windows.com bn4sch101120913.wns.windows.com bn4sch101121019.wns.windows.com bn4sch101121109.wns.windows.com bn4sch101121118.wns.windows.com bn4sch101121223.wns.windows.com bn4sch101121407.wns.windows.com bn4sch101121618.wns.windows.com bn4sch101121704.wns.windows.com bn4sch101121709.wns.windows.com bn4sch101121714.wns.windows.com bn4sch101121908.wns.windows.com bn4sch101122117.wns.windows.com bn4sch101122310.wns.windows.com bn4sch101122312.wns.windows.com bn4sch101122421.wns.windows.com bn4sch101123108.wns.windows.com bn4sch101123110.wns.windows.com bn4sch101123202.wns.windows.com bn4sch102110124.wns.windows.com

bongochong commented 3 years ago

This might be a tough nut to crack. These entries are used by a number of respectable anti-telemetry block lists for Windows users (e.g. Encrypt The Planet, SpyBot Anti-Beacon, CrazyMax) and I don't want to hastily remove such a large amount of entries that have been confirmed as sources of telemetry by a variety of parties. They don't seem to cause problems with OneDrive under my Windows 7 and 8.1 installations when included in those hosts files either. Please whitelist them on your personal device(s) while I explore this for now.

What filtering setup are you using my list(s) in conjunction with by the way?

bongochong commented 3 years ago

Well for now, starting with commit 8cabf45, my MiniList block lists will no longer contain such entries until further notice. I cannot in good conscience remove them from my standard lists at this time, but seeing as the MiniList variants of my lists are meant to be less aggressive, it makes sense to mitigate this issue in those. Feel free to subscribe to the aforementioned lists instead of my standard ones, or to continue using my standard lists with a personal whitelist for the entries in question.

p1r473 commented 3 years ago

I'm using your lists in my PiHole I've whitelisted them on my end Thanks

bongochong commented 3 years ago

No problemo! Still looking into addressing this issue across all of my lists, but I think the MiniList compromise is a good move for now. There's a lot of documentation regarding OneDrive, a big list of endpoints, and some testing I have to do on my Windows boxes to see if these domains can be removed from all of my lists, that is, unless one or more of the upstream sources I mentioned makes a change or statement regarding them, which would speed things along considerably. I have used Pi-hole, OpenWrt +plugins, and other network-wide DNS-based filtering solutions in the past at home, but found that - as a list maintainer - it was more sensible to handle most of my filtering on a client-by-client / device-by-device basis, as it allows for easier troubleshooting. As always, many thanks for bringing this to my attention.

bongochong commented 2 years ago

Small update: After some digging and research, I have concluded that the *.1drv.com entries are valid OneDrive endpoints that have mistakenly ended up in many, many other anti-windows telemetry lists. I have removed those entries from the relevant lists in my repo. As for the *.wns.windows.com entries, I cannot find any documentation from Microsoft regarding their connection to OneDrive functionality, so those will remain in my standard lists (though they will still be excluded from the MiniList variants).