Re:Google mitigated the largest DDoS attack to date, peaking...
by soperj on Tuesday October 10, 2023 @11:12AM
(#37833109)
Patch what though?
They know that they're getting hit with unprecedented traffic, not how those computers were infected.
[ Parent
| on HN ]
Re:Google mitigated the largest DDoS attack to date, peaking...
by menscher on Tuesday October 10, 2023 @11:47AM
(#37833671)
It's mostly not infected computers, but rather poorly configured proxies that are open for anyone to bounce malicious traffic through. Convincing everyone to clean up their open proxies is a long-term, hard problem. But I plan to tackle it soon....
Re:Google mitigated the largest DDoS attack to date, peaking...
by superjan on Tuesday October 10, 2023 @12:14PM
(#37834057)
How? I suppose the most effective way is to have those proxies attack each other. But don’t, it’s likely illegal.
Re:Google mitigated the largest DDoS attack to date, peaking...
by soperj on Tuesday October 10, 2023 @12:54PM
(#37834543)
the most efficient way would be to write a script that gains root on those open proxies and then fixes the issue.
Re:Google mitigated the largest DDoS attack to date, peaking...
by wsintra2022 on Tuesday October 10, 2023 @02:01PM
(#37835331)
Effective or efficient?
Would seem rather inefficient to spend time researching all the possible ways to gain route on x number of servers, finding an exploit, crafting some plan to execute it, keeping your prints clean etc etc
Re:Google mitigated the largest DDoS attack to date, peaking...
by soperj on Tuesday October 10, 2023 @02:15PM
(#37835500)
What way would be more efficient?
Re:Google mitigated the largest DDoS attack to date, peaking...
by menscher on Tuesday October 10, 2023 @07:18PM
(#37839013)
Get a few companies to agree that open proxies are a scourge that needs to be stopped. They each apply some action to open proxies (user-facing messaging, loss of functionality, captcha, or complete block), and the users of those proxies will get the problem fixed.
The hard part (and it truly is hard!) is convincing a few companies to do this. It risks user complaints in the short term, to solve a problem that may not be very acute for the largest companies (who can simply absorb these attacks).