IP level blocking for Tor Browser and Firefox #1737
Replies: 4 comments 10 replies
-
IF, this idea get passed through the filter and end up as code I would recomment to set a requirement for the CIDR (subnet) value. Why? It would add full cross project support between BlackList systems like uBlock adblock etc and RPZ (https://mypdns.org/mypdns/support/-/wikis/RPZ-record-types#the-client-ip-address-trigger-rpz-client-ip-anchor-clientip) and it will help ensuring only the relevant network will become blocked. My initial 2 cents |
Beta Was this translation helpful? Give feedback.
-
IP addresses are not known before a server responds to a network request, and for Chromium-based browsers, it's even at response body time (if I remember correctly), at which point it's not possible to block. The |
Beta Was this translation helpful? Give feedback.
-
Okay, so I lack insider info on how AdGuard's |
Beta Was this translation helpful? Give feedback.
-
uBlock having a kind of like /etc/hosts to block IP/CIDR will be amazing! Its called uBlock after all, it should be thought of like firewall for browser. |
Beta Was this translation helpful? Give feedback.
-
There are a lot of cases where blocking on the IP level could be helpful (i.e. uBlockOrigin/uAssets@56da93d, although there's probably better)
I know AdGuard's App has $network for that, although I have not had a chance to figure out exactly how it works
I understand this would be a lot of work, but it could be very helpful when fighting malware, or even blocking ads/trackers
What does everyone think?
CCing @DandelionSprout
Beta Was this translation helpful? Give feedback.
All reactions