Serious Question: How Long?

2 years is what I saw on you tube

Iā€™m a professional in this, youā€™re some jackass who read some paper online and thinks he knows everything about it, like I donā€™t already know whatā€™s in it? How stupid are you?

Iā€™m just a software developer. But I know that DDOS isnā€™t going to get outsmarted by some load balancing. If it were, this problem would have gone away entirely by now. We wouldnā€™t need threat maps or action plans.

Try harder.

Yeah, so you donā€™t know sh.t about database engineering, infrastructure and design. Cool.

This isnā€™t like a lock and key. Itā€™s a competition between how big the spam is, vs how well the target can endure it, basically gun vs armor, or flood vs damn. A big enough DDOS can bring down any server. Counter measures revolve around being able to handle the load without regular users noticing itā€™s there. If the server can handle every regular connection, on top of all the spam, then no one notices a problem. The problem comes when servers can no longer handle all the traffic, usually caused by a flood of gibberish spam.

It doesnā€™t really matter if this continues forever. Blizzard will just keep adding more servers to handle the traffic until the DDOS has reached its peak. After that, the attack will become irrelevant. When their paying customers are unable to play, you can bet thereā€™s a high priority on upgrading or adding hardware to increase the traffic load. The DDOS would have to be progressively bigger, costing more and more, to remain relevant. Pretty sure Blizzard has more money than they do.

1 Like

Why is this sad? Theyā€™re doing it fully aware of possible repercussions, I say any punishment they get is what they deserve.

Again: if this sort of attack were so easy to fix, it wouldnā€™t be such a common attack. Itā€™s effective because the only way to really stop it is to track down and arrest the perpetrator.

Itā€™s happening right now. I donā€™t know how to make this any clearer to you.

1 Like

Imo, itā€™s not sad in the sense that they are punished. Itā€™s sad that somebody is so arrogant that they are willing to lose time as a free person over what amounts to disrupting a video game. The stupidity of it is sad. People go to jail for all sorts of really bad things, and this person is so stupid and arrogant that they are willing to risk that punishment for this. Itā€™s likely some dipstick laughing up and shrugging off the potential consequences. But, then they could get caught and slammed with several years in jail. It saddens me that such a thing would happen to anybody, even those that deserve it, because I know how valuable that time is.

But, people make their choices, right?

Itā€™s a common attack because of the data infrastructure people who get attacked by it are using, like Blizzard. If it was impossible to stop DDoS attacks things like google would have been downed a long time ago by state actors.

Distributed infrastructures mean that no one piece of hardware is running the whole server at once, the virtual server is running on many machines, which could all be using different network paths. When an attack like this happens it just shifts the load to other machines systematically, which is load balancing. This is something that more and more companies have started using in the past 10 years, it wasnā€™t really available before that, which is why these attacks stay common.

Go write whatever sh.tty software it is you write and let people who actually build and manage databases talk about things they actually know about.

3 Likes

No. Like I mentioned above, the actual AWS threat mitigation documentation is available for anybody to read. This guy wants to put blame on the victim because heā€™s irritated about his 15 bucks.

this is my favourite thread

4 Likes

Lol. No. Go read the documentation.

If the DDoS is not discovered right away, the damage is done, might be why we are still unable to play todayā€¦

yeah, but those companies are gross. Especially with what theyā€™ve been doing poltically/socially.

2 Likes

No matter what infrastructure you use, being targeted by a DDOS attack WILL affect you and your audience. No amount of distribution and redundancy can give you complete protection, because of how the internet works. Thereā€™s no perfect world where itā€™s only going to affect this one physical server. No, itā€™s going to affect every server that gets routed to.

Now it IS preventable. As soon as this unusually high traffic gets detected, thereā€™s systems that can immediately reroute all traffic, essentially cutting you off from the internet. That is an aweful idea in an MMOG or really any high traffic server, because that means that any unusually high volume of legitimate players, like after any times servers have to come down on a tuesday, will trigger the same result. And because WoW players, that would be over and over, indefinitely. Basically, if Blizzard took steps to prevent DDOS attacks, the entire game would still be down thanks to the initial surge of traffic 2 weeks ago. We would have never logged into classic.

All you can really do about a DDOS attack is let your ISP know so that they can reroute any new connections away from you, and then you just have to wait until its over.

Congratulations, you manage databases. Too bad a DDOS attack targets a server, which actually falls on the software development side. You might want to listen to him, he knows what heā€™s talking about. Database management is pretty much the entry level of IT.

2 Likes

I love you.

At absolute best, and i mean the absolute extreme best, perhaps as long as a month.

By that time though, there will be a trail of evidence leading Blizzard straight to the person(s) responsible, law enforcement will have been engaged to deal with it and the resulting prison time and legal cases that arise from it would mean the end of that person or persons attacks.

The more likely outcome is maybe a week at best, anything longer and they seriously risk exposing themselves. There is a good chance Blizzard already have all the evidence they need to track them down and prosecute, but that takes time of course.

You are seriously dense dude, youā€™re going to tell someone whose job it is to do these kinds of things, as someone who works in a totally different field, that they are wrong and should read a paper that suddenly made you a professional in the subject by reading it?

Lol.

I build Azure databases, I donā€™t just ā€˜manageā€™ them. You also have no idea what the hell you are talking about.

Iā€™m a professional by trade. I read documentation like this when I evaluate software. Itā€™s pretty standard.

I donā€™t know how to make this easier for you. If it were so easy to prevent, this functionality would have been abstracted away (such that it can be used by any system) and there would be no such thing as a DDOS threat.

Try. Again.