Is blocking all of the "Suspicious IPs" a sane idea? #5323
Unanswered
mbledkowski
asked this question in
Q&A
Replies: 1 comment 3 replies
-
|
Accept only the incoming requests from IPv4 .. the IP ranges in IPv6 are to big to effective detect suspicious ones .. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have noticed a lot of bot activity on my instance, which causes me, to get rate limited by almost all of the popular search engines.
From what I see, basically every block from ip limiter is made to suspicious IPs. It could be a survivorship bias, but I forked searxng, and made all of the limiter values lower (BURST_MAX and other *_MAX values), and still only suspicious ips are blocked, so I think this is unlikely.
What are the examples of genuine users, that could be marked as suspicious IPs? From what I can tell, suspicious IPs are those that do not load css, where I think even the paranoid users, block JS, but not CSS (see Tor Browser).
If I decide to block all of the suspicious IPs, would that still be in the spirit of the SearXNG project. The reason why I have not put my instance behind Cloudflare DDOS protection, is exactly because it is against the values of this project, and I would like for my instance to be with agreement with those.
Best regards,
Maciej Błędkowski
Beta Was this translation helpful? Give feedback.
All reactions