Re:Let us serve you, but don't bring us down
by Taek on Monday May 29, 2023 @12:49AM
(#36110764)
I don't think that works if your attacker has millions of IPs and is only using 200 per second.
[ Parent
| on HN ]
Re:Let us serve you, but don't bring us down
by akiselev on Monday May 29, 2023 @01:01AM
(#36110832)
How are they getting millions of ipv4 addresses? IIUC that’s at least the equivalent of a /12 block. Do those shady residential proxies really operate at that scale?
If they’re ipv6 address wouldn’t they be safe to block across large ranges?
Re:Let us serve you, but don't bring us down
by slivanes on Monday May 29, 2023 @01:05AM
(#36110864)
My guess through compromised boxes (or some apps) that act as proxies.
Re:Let us serve you, but don't bring us down
by reaperman on Monday May 29, 2023 @01:11AM
(#36110901)
It is trivially easy to get millions of IPv6’s, even spread out across a thousand ranges.
It is also trivially “easy” to get past reCAPTCHA, but it costs more. My guess is that a domain name checker tool isn’t worth the cost per request to bypass reCAPTCHA (approximate 0.02 cents per session)
Re:Let us serve you, but don't bring us down
by jszymborski on Monday May 29, 2023 @01:22AM
(#36110943)
Right, but this is why the GGP's post suggested throttling IPV6. Or at least that was my understanding.
Re:Let us serve you, but don't bring us down
by reaperman on Monday May 29, 2023 @01:31AM
(#36110980)
The 500ms latency will help a lot if tons of requests are coming in serial. But most likely they are coming in parallel.
It’s hard to “throttle” a single isolated request from a lone IP.
So.. make the requests serial. Just dump all the requests coming in over IPv6 into a queue, service that queue at a rate that's higher than the non-bot traffic requires but still low enough to be a problem for bots that can't self-limit to a reasonable rate. And of course, manage that queue intelligently so that you start dropping requests before you run out of RAM.