News for hackers. Stuff that matters.
Re:Google mitigated the largest DDoS attack to date, peaking... by DanielBMarkham on Tuesday October 10, 2023 @09:03AM (#37831528)
Why don't we just require major providers to provide a realtime list of IPs that are attacking so that we can drop them in a block list with an expiration date of a month or so.

If your computer is infected, I don't want to talk to you for a month. If it continues to be infected, I might up that to a year, or permanently ban you.

It's your problem. Go fix it.

Re:Google mitigated the largest DDoS attack to date, peaking... by Prickle on Tuesday October 10, 2023 @09:17AM (#37831668)
I've been on the receiving end of "Your" (dynamic) "IP has been blocked."

I would greatly prefer not having my semi-randomized IP blocked because someone used it maliciously a year ago.

Re:Google mitigated the largest DDoS attack to date, peaking... by DanielBMarkham on Tuesday October 10, 2023 @09:29AM (#37831834)
Key phrase: "a year"

If anybody is suggesting permanent bans of IPs, it's not me, at least not at a public level. I may very well choose privately to do that.

To clarify, me, personally chooses a blacklist policy. Not some other org. I think if you offload this onto any kind of external structure, it breaks again.

There's a huge commerical interest in NOT fixing the problem of random crap showing up, from dancing cats selling things to targeted inserted ads. I get it. We saw this same thing happen with adblockers. It's now going on with "free" VPNs. Can't fight that perverse incentive, so don't fight it.

Re:Google mitigated the largest DDoS attack to date, peaking... by tristan9 on Tuesday October 10, 2023 @10:07AM (#37832311)
Thing is, don’t care.

The problem is that ISPs whose customers are originating the attacks from don’t give a shit.

If we have to give up 1% of legitimate traffic to thwart 90% of attacks, it is a good deal.

If you and other customers complain to your ISP (or switch), eventually they’ll do something about it.

We can’t seriously keep on accepting that « thousands of compromised devices » is a fine reality for a « small botnet ».

These devices should be quarantined.

Re:Google mitigated the largest DDoS attack to date, peaking... by dist-epoch on Tuesday October 10, 2023 @10:33AM (#37832635)
Amazon definitely cares if they lose 1% of sales.

Guess who has more votes, you or Amazon.

Re:Google mitigated the largest DDoS attack to date, peaking... by tristan9 on Tuesday October 10, 2023 @08:23PM (#37839514)
I’m aware. Doesn’t make it sting less being in the receiving end of attacks all the time and seeing everyone collectively shrug.
Re:Google mitigated the largest DDoS attack to date, peaking... by InSteady on Tuesday October 10, 2023 @01:50PM (#37835194)
Sounds like a really great way to potentially destroy someone's career if they aren't terribly competent and you are. Infect some component in their home network that they don't even know is smart-enabled, and keep breaching their new devices, adding them to an active and conspicuous botnet. The only recourse for average Joe is to find expert help, which isn't really in abundant supply if you are a semi-sophisticated malicious actor.

I don't even want to think about the ramifications for small and medium sized businesses. Realistically, how much would it cost to be able to completely destroy a local competitor by paying someone to orchestrate a few events in succession.

Re:Google mitigated the largest DDoS attack to date, peaking... by DanielBMarkham on Tuesday October 10, 2023 @05:43PM (#37838003)
This is an odd argument. The net is currently broken in many ways. One of the many ways is fake negative reviews. They easily destroy small businesses.

As I understand your argument, because the net has solid endpoints we can identify and isolate, we should ignore that fact. Instead we should create more and more complex systems to work around bad actors?

Bad actor takes control of grandma's computer. We should do all sorts of things except stop talking to grandma's computer? The thing, I would suspect, that most people would expect?

Businesses suffer from too much transparency. Got that part. They buy things that don't work and sometimes hurt people, even if they don't intend to do this. So far, so good. Where is the part where new businesses models are supposed to exist because some people made bad choices and the current models don't work? Why don't we just publicize the bad choices and let things work themselves out?

Sorry. Missing it.

Re:Google mitigated the largest DDoS attack to date, peaking... by Prickle on Wednesday October 11, 2023 @08:02PM (#37851947)
Ok, that is somewhat fair.

My personal want / solution would simply be "everything gets an IPV6, and IPV4 gets deprecated. Everything using IPV4 gets an algorithm slapped on top to covert it into IPV6.

Dynamic ips become a thing of the past.

But I realize that is significantly easier said than done. (Makes Minecraft servers easier to setup though)

Re:Google mitigated the largest DDoS attack to date, peaking... by scrpl on Tuesday October 10, 2023 @09:11AM (#37831617)
Great solution for a world without shared and dynamic ips.
Re:Google mitigated the largest DDoS attack to date, peaking... by nine_k on Tuesday October 10, 2023 @09:26AM (#37831793)
Not as bad as one may think. It's proper feedback which can be acted upon.

Every reasonable connectivity provider would pay attention to this info, or face intense complaints from its users with shared and dynamic IPs. It would identify sources of attacks, and block them at higher granularity level, reporting that the range has been cleared. (If a provider lied, everyone would stop believing it, and the disgruntled customers would leave it.)

For shared hosting providers it would mean blocking specific user accounts using a firewall, notifying users, and maybe even selling cleanup services.

For home internet users, it also would mean blocking specific users, contacting them, helping them identify the infected machine at home.

It would massively drive patching of old router firmware which is often cracked and infected. Same for IoT stuff, infected PCs, malicious apps on phones, etc. There would be an incentive to stay clean.

Re:Google mitigated the largest DDoS attack to date, peaking... by scrpl on Tuesday October 10, 2023 @09:35AM (#37831912)
If the one doing the blocking is not at FAANG it would do nothing of sorts. And FAANG benefit from DDoS by getting people into their walled cloud gardens.
Re:Google mitigated the largest DDoS attack to date, peaking... by ilyt on Tuesday October 10, 2023 @09:31AM (#37831857)
Funny man, thinks big ISP cares you yourself blocked your own site from your own customers coming from the big ISP network.
Re:Google mitigated the largest DDoS attack to date, peaking... by nine_k on Wednesday October 11, 2023 @09:09AM (#37843899)
No; with a shared hosting, somebody else manages to blacklist the IP that serves many paying customers.
Re:Google mitigated the largest DDoS attack to date, peaking... by dmm on Tuesday October 10, 2023 @09:14AM (#37831637)
Block the whole subnet and make it the ISP's problem?
Re:Google mitigated the largest DDoS attack to date, peaking... by cryptonym on Tuesday October 10, 2023 @09:17AM (#37831670)
Because when a single machine is infected, at one ISP, it's a good idea to block the whole subnet? I don't think any commercial activity could afford such security strategy, blindly blocking legit users by thousands.
Re:Google mitigated the largest DDoS attack to date, peaking... by DanielBMarkham on Tuesday October 10, 2023 @09:23AM (#37831738)
It's interesting to me that most of the push-back so far has been for the business model of the internet, ie people need link traversal and content publishing in order to make money from advertising (implied, but not stated). Therefore we need to add yet another layer to the mix, the cloud providers, and start paying those guys.

And yes, we can block entire subnets. You own the IP addresses, you're responsible for stuff coming out of them, at least to the degree that it's not maliscious to the web as a whole. (but not the content itself, of course)

Bullshit. The internet is a communications tool. If it's not communicating, it's broken. If you provide dynamic IPs to clients that attack people, you're breaking it. It's not my problem or something I should ever be expected to pay for.

To be clear, my point is that we're suggesting yet another layer of commercial, paid crap on top of a broken system in order to fix it. It'd be phenomenally better just to publicly identify place and methods where it's broken and let other folks with more vested interests than information consumers worry about it. Hell, I'm not interested in paying for the current busload of bytes I'm currently consuming for every one sentence of value I receive.

Re:Google mitigated the largest DDoS attack to date, peaking... by scrpl on Tuesday October 10, 2023 @09:37AM (#37831937)
I‘m sure comcast is terrified that their users won’t be able to read my blog.
Re:Google mitigated the largest DDoS attack to date, peaking... by judge2020 on Tuesday October 10, 2023 @09:18AM (#37831676)
How does the ISP solve it? Send a mass mail/email telling people to reset their devices because someone has a device with botnet malware?
Re:Google mitigated the largest DDoS attack to date, peaking... by AnimalMuppet on Tuesday October 10, 2023 @09:27AM (#37831808)
Egress filtering? A botnet DDOS stream should not look like normal network traffic...
Re:Google mitigated the largest DDoS attack to date, peaking... by bluGill on Tuesday October 10, 2023 @10:05AM (#37832272)
That is their problem. Maybe the price needs to go up if you don't secure all your devices as the ISP is going to send a tech to your house. Or maybe the ISP has deep enough pockets to find a sue those cheap IOT device makers for not being secure thus funding their tech support team.
Re:Google mitigated the largest DDoS attack to date, peaking... by tmpX7dMeXU on Tuesday October 10, 2023 @09:22AM (#37831729)
You are quite obviously speaking from the perspective as someone that wouldn’t be in a position to be making these calls.
Re:Google mitigated the largest DDoS attack to date, peaking... by swarnie on Tuesday October 10, 2023 @09:18AM (#37831681)
> Sorry citizen, google services are inaccessible because the only ISP in your city sold a service to a bad actor.

> We might fix this, we might not, you DONT have a choice.

> Thank you for your continued business.

Re:Google mitigated the largest DDoS attack to date, peaking... by tmpX7dMeXU on Tuesday October 10, 2023 @09:25AM (#37831766)
Hacker News nerds will argue all day long that the Internet is a utility when the argument happens to personally benefit them, then in the same breath say that a random network admin is justified in blocking a whole ISP subnet due to one “bad” actor. And of course by bad actor I mean person that almost certainly accidentally got themselves infected with malware by not understanding the completely Byzantine world of computers and the Internet.
Re:Google mitigated the largest DDoS attack to date, peaking... by grotorea on Tuesday October 10, 2023 @08:46PM (#37839661)
Well, if someone had somehow gotten their house wires damaged in a way that causes brownouts to neighbours, wouldn't the electric company be justified in cutting off the house?
Re:Google mitigated the largest DDoS attack to date, peaking... by phone8675309 on Tuesday October 10, 2023 @09:21AM (#37831715)
Indistinguishable from the kind of service I get from Google - the moment that I need a human involved I just close my account with whatever Google service is misbehaving and move on.
Re:Google mitigated the largest DDoS attack to date, peaking... by swarnie on Tuesday October 10, 2023 @10:12AM (#37832368)
But you have other options which is my point.

(swap in any corpo-service provider you personally like the most)

Blanket banning subnet ranges from services because of the actions of someone else is 3rd world shit.

Re:Google mitigated the largest DDoS attack to date, peaking... by phone8675309 on Tuesday October 10, 2023 @09:20AM (#37831703)
So it’s the ISPs fault that my grandma never met a spam email that she didn’t want to click?

One of the things that gets lost in this kind of debate is that the vast, vast majority of Internet users are not experts in how the Internet, computers, or their phones work. So expecting them to be able to "just not get exploited" is a naive strategy and bringing the pain to the ISP feels counterproductive because what, realistically, can they do to stop all of their unsophisticated users from getting themselves exploited?

At the end of the day, the vast majority of the users of the Internet do not care how it works - they want their email, they want their cat videos, and they want to check up on their high school ex on Facebook. How can we rearchitect the Internet to be a) open b) privacy protecting, and c) robust against these kinds of attacks so that the targets of DDOS attacks have better protection than paying a third party and hoping that that third party can protect them?

Re:Google mitigated the largest DDoS attack to date, peaking... by lapcat on Tuesday October 10, 2023 @09:20AM (#37831706)
"Moreover, the lifespan of a given IP in a botnet is usually short so any long term mitigation is likely to do more harm than good." "As we can see, many new IPs spotted on a given day disappear very quickly afterwards." https://blog.cloudflare.com/technical-breakdown-http2-rapid-...
Re:Google mitigated the largest DDoS attack to date, peaking... by afavour on Tuesday October 10, 2023 @09:10AM (#37831592)
Banning a large number of customers for an entire month? doesn’t make economic sense, it’ll be cheaper to just pay a big cloud provider for protection.

(not to mention the number of false positives you'd get, etc etc)

Re:Google mitigated the largest DDoS attack to date, peaking... by codedokode on Tuesday October 10, 2023 @09:26AM (#37831786)
I propose to make a special "reject" packet. When a host, let's say 1.1.1.1, sends such packet to 2.2.2.2, all providers that see this packet, MUST reject any traffic from 2.2.2.2 to 1.1.1.1. This is very easy but very efficient and allows a single host to withstand the attack of any size.

There is no need for any central authority and no need to maintain any lists.

Re:Google mitigated the largest DDoS attack to date, peaking... by Swenrekcah on Tuesday October 10, 2023 @09:31AM (#37831863)
That actually sounds like a really good idea. This is already implemented in the physical world (in a much less efficient way) in the form of “no spam” stickers and registrations.

Is there a reason other than inertia for why it hasn’t been implemented?

Re:Google mitigated the largest DDoS attack to date, peaking... by codedokode on Tuesday October 10, 2023 @09:39AM (#37831957)
ISPs do not want to spend money for fighting against criminals.
Re:Google mitigated the largest DDoS attack to date, peaking... by Swenrekcah on Tuesday October 10, 2023 @09:42AM (#37831988)
That doesn’t sound convincing to me. I mean I understand they don’t want to spend money but if cost is the only barrier it seems like that could be overcome somehow by interested parties.
Re:Google mitigated the largest DDoS attack to date, peaking... by bombcar on Tuesday October 10, 2023 @10:34AM (#37832644)
It's not the costs, it's that some ISPs like getting money from spammers and criminals, and carefully look the other way.

And the other ISPs like getting paid for DDoS mitigation, so they also look the other way. There's no money to be made fixing the underlying problem.

Re:Google mitigated the largest DDoS attack to date, peaking... by bombcar on Tuesday October 10, 2023 @10:33AM (#37832634)
The main problem is how do you authenticate the request as being legitimate? It's already possible to spoof headers and "FROM-IP" (in fact, major DDoS attacks use just this as a replay attack, spoof a DNS request as coming from 1.1.1.1 and get a much larger response sent TO 1.1.1.1 from wherever).
Re:Google mitigated the largest DDoS attack to date, peaking... by codedokode on Tuesday October 10, 2023 @01:57PM (#37835279)
You can send back a reply with a token to confirm ban.
Re:Google mitigated the largest DDoS attack to date, peaking... by KomoD on Tuesday October 10, 2023 @11:16AM (#37833157)
And then that can be abused...
Re:Google mitigated the largest DDoS attack to date, peaking... by codedokode on Tuesday October 10, 2023 @01:58PM (#37835285)
No, it cannot. It is well-thought.
Re:Google mitigated the largest DDoS attack to date, peaking... by TheDong on Tuesday October 10, 2023 @07:50PM (#37839254)
There are 2^128 ipv6 addresses.

If you store 1 bit (banned/unbanned) + a unix timestamp (ban expiration) for each of those IPs, that requires more storage space than exists many billion times over.

To store such a block table you propose would require more memory for routers than any router has ever had and ever will have.

An attacker could easily "flush" all entries in this table by, for example, banning a TB of ipv6 addresses from talking to them, surely resulting in all participating routers dropping other bans to store some of those.

Re:Google mitigated the largest DDoS attack to date, peaking... by codedokode on Wednesday October 11, 2023 @09:40AM (#37844241)
We can store an IP address with a mask (ban subnets instead of separate addresses). Also, IPv6 is so rarely used, that I would ban whole address space for the time of attack.

For example, if an attack is coming from a country you where you don't have many paying customers, but where there are many infected devices due to use of pirated outdated software, it is easier to ban the whole country than to figure out who is infected and who is not.

Re:Google mitigated the largest DDoS attack to date, peaking... by codedokode on Wednesday October 11, 2023 @09:40AM (#37844251)
> An attacker could easily "flush" all entries in this table by, for example, banning a TB of ipv6 addresses

We can set a limit of ban records per host to prevent it.

Re:Google mitigated the largest DDoS attack to date, peaking... by sgjohnson on Wednesday October 11, 2023 @09:53PM (#37852603)
ban the entire /64. If banning the /64 is not enough, then ban the /48. If that is not enough, keep going up 4 bits until it is (most IPv6 allocations line up on a nibble boundary, hence the 4 bits)
Re:Google mitigated the largest DDoS attack to date, peaking... by ilyt on Tuesday October 10, 2023 @09:30AM (#37831839)
And now some of your services don't work because you blocked IP that turned out to be cloud service IP being reused for legit service
Re:Google mitigated the largest DDoS attack to date, peaking... by fragmede on Tuesday October 10, 2023 @09:28AM (#37831821)
You're assuming that identification of attack traffic is 100% correct which is unfortunately not the reality.
Re:Google mitigated the largest DDoS attack to date, peaking... by smath on Tuesday October 10, 2023 @10:08AM (#37832317)
That would be giving away some of the secret sauce on the part of the cloud providers. They are selling security as (part of their) service. There are some community shared lists of botnets ofcourse, but they may not be vry real time or very up to date.