EnergizedProtection / block

Let's make an annoyance free, better open internet, altogether!
https://energized.pro
MIT License
2.46k stars 198 forks source link

Several changes to blocklist(s) #485

Open TheNec opened 4 years ago

TheNec commented 4 years ago

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

Provide the following infos properly, which will help us to resolve your issue quickly.

Issue(s):

Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x] You can select more than one category of issues if you need to!


Pack(s):

Write the name of the pack(s) you are using.

Extension(s):

Also name the extension(s) if you are using any. If you don't then leave it blank.

Domain(s):

If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.


Your Config:

Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list. Make sure you are running Energized Protection Service only.

Details:

Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Please REMOVE DOMAIN 'hitfile.net' | file hosting service Please REMOVE DOMAIN 'hitf.to' | link shortener of above 'hitfile.net' Please REMOVE DOMAIN '(www.)pc-magazin.de' | online IT magazine Please REMOVE DOMAIN 'abload.de' | picture hosting service Please REMOVE DOMAIN '(www.)volksverpetzer.de' | fact checker/publisher against fake news Please REMOVE DOMAIN '(www).cutcaptcha.com' | captcha service Please REMOVE SUBDOMAIN/SUBDOMAINS OF 'update.microsoft.com' | breaks Microsoft updates Please REMOVE SUBDOMAIN/SUBDOMAINS OF 'mp.microsoft.com' | breaks Microsoft updates Please REMOVE SUBDOMAIN/SUBDOMAINS OF 'windowsupdate.com' | breaks Microsoft updates Please REMOVE DOMAIN/SUBDOMAINS OF 'wfcdn.de' | content delivery network of online IT magazine 'winfuture.de' / breaks the page / does not deliver ads Please REMOVE SUBDOMAINS OF 'ioam.de' and ADD DOMAIN 'ioam.de' entirely | tracker 'service'

Thanks for your work and thank you in advance!


Thank you for making Energized Protection great, with your kind help!

A project by Ador with ❤
ghost commented 3 years ago

hitfile.net hitf.to www.pc-magazin.de abload.de www.volksverpetzer.de www.cutcaptcha.com .update.microsoft.com .windowsupdate.com

seem resolved, not appearing on today's Ultimate | Regional set.


*.mp.microsoft.com

Unless mistaken MP probably relates to something phone (Microsoft Phone or Mobile Phone) but I could not reproduce:

'mp.microsoft.com' | breaks Microsoft updates

Might be better to get those sorted at the respective upstream source


*.ioam.de ioam.de

Are actual user profile trackers, part of https://www.infonline.de/en/, and should not be globally whitelisted. If a user elects to be tracked such should be whitelisted locally on the user's node instead.


*.wfcdn.de

Whilst being a CDN for winfuture.de the content admin choose to delivery ads though it (embedding) and therefore it should not be globally whitelisted but instead locally on the user's node, if such is the user's preference.

ghost commented 3 years ago

*.mp.microsoft.com

Unless mistaken MP probably relates to something phone (Microsoft Phone or Mobile Phone) but I could not reproduce:

'mp.microsoft.com' | breaks Microsoft updates

* `*-prod.do.dsp.mp.microsoft.com ` entries stemming from https://block.energized.pro/assets/sources/filter/airelle-trc.txt

Might be better to get those sorted at the respective upstream source

*.prod.do.dsp.mp.microsoft.com is mentioned by MS as connection endpoints for non-Enterprise editions but being cited in various public places as MS telemetry domains (apparently Enterprise editions can do without...). If it really breaks WIN updates the matter should probably addressed with the upstream source (Airelle).

TheNec commented 3 years ago

Thanks for your response! =)

*.mp.microsoft.com

Unless mistaken MP probably relates to something phone (Microsoft Phone or Mobile Phone) but I could not reproduce:

'mp.microsoft.com' | breaks Microsoft updates

I can reproduce it and if I whitelist this domain manually it works so if you don't have those problems than you shouldn't judge ;)

*.prod.do.dsp.mp.microsoft.com is mentioned by MS as connection endpoints for non-Enterprise editions but being cited in various public places as MS telemetry domains (apparently Enterprise editions can do without...).

If you have a specific version installed you need to tell it to the update server so that it can provide you the update package you need. This is telemetry! And even if you would do this on the client before the server would know it because of the requested package. Otherwise you would always need to download a full installation package! But hey. As some people started to cry some years ago that telemetry is evil because Microsoft uses it (at least since Vista btw.) it must have been invented by the devil itself ;)

Edit: In this case "geo-prod.do.dsp.mp.microsoft.com" seems to be a server for "Delivery Optimization" as stated here: https://social.technet.microsoft.com/Forums/en-US/77f5642d-77b9-45eb-8ec4-c9eee225c39a/in-case-of-fiewall-block-to-access-quotdodspmpmicrosoftcomquot?forum=win10itpronetworking

My best guess is that this is mostly a geo location service (telemetry again!!!111) for determining the best update server that is accessed after you told Microsoft anyway where you are when searching for updates.

* `licensingphone.mp.microsoft.com` stems from https://block.energized.pro/assets/sources/filter/1hosts.cf-pro.txt

* `*-prod.do.dsp.mp.microsoft.com ` entries stemming from https://block.energized.pro/assets/sources/filter/airelle-trc.txt

If it really breaks WIN updates the matter should probably addressed with the upstream source (Airelle).

Might be better to get those sorted at the respective upstream source

This may be correct but if I need to address such changes to the upstream sources then this option would be really unnessesary in this repository ;)

*.ioam.de ioam.de

Are actual user profile trackers, part of https://www.infonline.de/en/, and should not be globally whitelisted. If a user elects to be tracked such should be whitelisted locally on the user's node instead.

I know that but this was not meant to be whitelisted completely. My intention was to clean up the lists. You do not need to use subdomains (e.g. script.ioam.de) when the whole domain (ioam.de) is blocked. Please read my issue details again but carefully ;)

*.wfcdn.de

Whilst being a CDN for winfuture.de the content admin choose to delivery ads though it (embedding) and therefore it should not be globally whitelisted but instead locally on the user's node, if such is the user's preference.

The page is not usable without scripts from the CDN. So either you visit it then you need them or you don't visit it then you don't need those entries on the list because it doesn't host any content for third parties. Thus it should be deleted in any way!

The best solution for this (and my dream :D) would be:

  1. Use one list that does only contain (full) ad/malware/tracker... domains (ideally as a network side DNS filter like pi-hole)
  2. Use a 2nd list (on application side / browser) that does not contain any entries from the first list and uses only adblock filters on the corresponding content for domains that also host legit stuff.

This would be the most performant choice especially for low hardwared mobile devices saving battery and is therefore also life-prolonging

ghost commented 3 years ago

I could not reproduce:

'mp.microsoft.com' | breaks Microsoft updates

I can reproduce it and if I whitelist this domain manually it works so if you don't have those problems than you shouldn't judge ;)

Nothing judgemental, just a statement of facts for my nodes, for which Delivery Optimization with peers over the internet is disabled via GPO and therefore not utilising those domains and updates are not being broken - different setup than your end it would seem.