4 ms·
That argument only holds true if the person operating the site has no idea at all about the HTTP standards. * GET requests have to be idempotent. * Security b
by kuschku 11y ago
That argument only holds true if the person operating the site has no idea at all about the HTTP standards.
* GET requests have to be idempotent.
* Security by Obscurity is not Security.
* Content Scraping is nothing you have to protect against, or should protect against – DRM just does not work.
- pfg 11y agoRight, but this is about abuse and solutions for that. Obviously, blocking Tor is not going to prevent a determined attacker from scraping your site or trying some SQLi vectors. It might, however, prevent a large number of bots from scraping your site for emails, scanning for vulnerabilities, or doing click fraud. It's not a perfect solution, but those rarely exist. CloudFlare sees a lot of malicious traffic, so they probably have a better view of what works and what doesn't compared to everyone else.
- kuschku 11y agoI see a lot of fraud on my site as well, and I can say that there are some ISPs in Eastern Europe and Asia that are just as likely as Tor as being the origin for a malicious attack. I don’t block them either. Instead, I use fail2ban with a 30min ban for the IP for all my servers, and have the rest of the system hardened. Also, I add an additional delay that’s just below the timeout that browsers have for each request from an IP of that block for the next 30min. Reduced my logs of "123.456.789.012 tried to authenticate as "root" with invalid password" from several gigabytes a day to a few kilobytes. ________________________ Sure, I don’t host a large site, or get much traffic, but saying "Tor is the only issue" or even "Tor is the largest issue" isn’t true. And there are solutions for these cases. Solutions which allow legitimate users to continue using the services.