pfBlockerNG wildcard blocking implementation is wack ?
-
Just found this on the OISD blocklist maintainer website:
"Note that pfBlockerNG does support wildcard blocking, but it's implementation is wack; It won't block subdomains to already listed subdomains, eg causing listed g.doubleclick.net to not block all of it's subdomains, which it should."
More discussion here
@BBcan177 what do you think about this ? -
@emikaadeo He already explain it here...see below. I can share that it works as intended for as long as I have used it...not a wack at all, that's just an opinion.
-
@nollipfsense said in pfBlockerNG wildcard blocking implementation is wack ?:
@emikaadeo He already explain it here...see below. I can share that it works as intended for as long as I have used it...not a wack at all, that's just an opinion.
I think that's not the point.
Everyone (including me) knows HOW wildcard blocking works in pfBlockerNG. The point is that the maintainers of the OISD and HaGeZi blocklists are wondering, WHY this funcionality is implemented in that way.
And I'm just sharing this discussion found on reddit. -
@emikaadeo Had the impression you created the post on Reddit. Whenever there is a design implementation and one ask why, one should immediately ask oneself, why not. I see no issue(s) with how it's done. If I were those maintainers, I would directly ask BBcan177 instead of publicly claiming it's wack as well as share how they would do it differently...simple respect, isn't it?
