Dyn DDoS this AM?
outsider at scarynet.org
Fri Oct 21 16:02:02 UTC 2016
Feel free to feed me with attack sources. Once those companies notice their precious mail does not arrive at clients. They will attempt to fix things. Sad but true.
- Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer
-------- Oorspronkelijk bericht --------Van: "Patrick W. Gilmore" <patrick at ianai.net> Datum: 21-10-16 17:48 (GMT+01:00) Aan: NANOG list <nanog at nanog.org> Onderwerp: Re: Dyn DDoS this AM?
I cannot give additional info other than what’s been on “public media”.
However, I would very much like to say that this is a horrific trend on the Internet. The idea that someone can mention a DDoS then get DDoS’ed Can Not Stand. See Krebs’ on the Democratization of Censorship. See lots of other things.
To Dyn and everyone else being attacked:
The community is behind you. There are problems, but if we stick together, we can beat these miscreants.
To the miscreants:
You will not succeed. Search "churchill on the beaches”. It’s a bit melodramatic, but it’s how I feel at this moment.
To the rest of the community:
If you can help, please do. I know a lot of you are thinking “what can I do?" There is a lot you can do. BCP38 & BCP84 instantly come to mind. Sure, that doesn’t help Mirai, but it still helps. There are many other things you can do as well.
But a lot of it is just willingness to help. When someone asks you to help trace an attack, do not let the request sit for a while. Damage is being done. Help your neighbor. When someone’s house is burning, your current project, your lunch break, whatever else you are doing is almost certainly less important. If we stick together and help each other, we can - we WILL - win this war. If we are apathetic, we have already lost.
OK, enough motivational speaking for today. But take this to heart. Our biggest problem is people thinking they cannot or do not want to help.
> On Oct 21, 2016, at 10:55 AM, Chris Grundemann <cgrundemann at gmail.com> wrote:
> Does anyone have any additional details? Seems to be over now, but I'm very
> curious about the specifics of such a highly impactful attack (and it's
> timing following NANOG 68)...
More information about the NANOG