Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Bgs <bgs@bgs.hu>
To: Martin McKeay <mmckeay@stillsecure.com>
Cc: Ric Messier <kilroy@WasHere.COM>, netfilter@lists.netfilter.org
Subject: Re: syn DDoS attack solution
Date: Tue, 05 Jun 2007 10:29:56 +0200	[thread overview]
Message-ID: <46651F04.9020709@bgs.hu> (raw)
In-Reply-To: <5C9E8CCEEB81ED498AC0C3B0054704F3029B6DE0@webmail.latis.com>

  You can have defense against many kind of ddos attacks but victory is 
not sure at all. Take the case for example when a very large number of 
distributed bots issues many but slow SYN/ACK bounce attacks or plain 
protocol connections to your site. If they do it 'right' you will end up 
with up to millions of sources doing 'ordinary' things with random 
sources. No source will ever trigger anything above an average user. One 
important step in taking ddos seriously was when the first ISP went 
broke because it was a target.

  So take up the fight when it happens. Most attackers are not 
resourceful enough (either by available hw/bots or technical knowledge), 
so on the long term you can usually win. But loosing the war is always a 
possibility no matter how good you are...

Martin McKeay wrote:
> I'm glad you summed up the technical aspects of the conversation so far.
> A DDoS attack is a serious problem, no matter what form it takes.
> 
> I have one question for you: do you really believe that there's no
> defense other than not waking the lion, that the battle is already lost?
> That doesn't paint a pretty picture to me.  Are you basing this on
> published work or personal experience?  Which I guess makes two
> questions, so I'll quit while I'm ahead.
> 
> Martin
> 
> Martin McKeay, CISSP, GSNA
> Cobia Product Evangelist
> StillSecure
> martin@stillsecure.com
> 707-495-7926
> http://www.cobiablog.com
> 
> -- R. DuFrense wrote --
> 
> 
> DDOS attacks work against resources, the tcp/ip stack <half opens
> (syn's) left hanging>, memory <cache of data in your syn-flood db>,
> drive space <system logs with overzealous logging of packet flow in
> limited space, or how much disk is devoted to a syn-flood db>, the size
> of your pipe...
> 
> 
> In any but the most simplistic low bandwith attacks there is little one
> can do in such cases but either ride out the storm or go upstream for
> help in resolution <mist often a block of the damaging traffic>.  Even
> an semi-decent firewall defense against a simple low bandwith syn flood
> will need to be totally rework for defense in the case of a simple
> lowbandwidth ping flood, etc.  And once the attack level is amplified
> above the flow capabilities of your pipe, all bets are off.  In a
> serious flooding attack the firewall simply become a stopgate from
> preventing work on the local net from being affected.  There have been
> and will continue to be some rather decently funded companies with some
> fairly decent pipes wiped out of business or their internet presence
> closed up due to some of these kinds of attacks over extended periods of
> time.  Goverments across the globe have had internet services disrupted
> for extended periods. 
> Microsoft has had to relocate servers to new net/ip addresses to divert
> the flow from such attacks and stay somewhat online...
> 
> 
> Best way to avoid such problems is to not get into a whose prick is
> bigger contest with some kid in IRC that controls a 10,000-100,000 or
> larger series of zombies in their botnet.
> 
> It's the nature of the game, all in the design...
> 
> 
> 
> Thanks,
> 
> Ron DuFresne
> - --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>          admin & senior security consultant:  sysinfo.com
>                          http://sysinfo.com Key fingerprint = 9401 4B13
> B918 164C 647A  E838 B2DF AFCC 94B0 6629
> 
> ...We waste time looking for the perfect lover instead of creating the
> perfect love.
> 
>                  -Tom Robbins <Still Life With Woodpecker> -----BEGIN
> PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> 
> iD8DBQFGYcADst+vzJSwZikRApiLAJ444UDiM3HZnoNLO7ECHocT31r88wCeMhmS
> Zv2jS1v6fCcb3gLbx9+KqHQ=
> =iZ/G
> -----END PGP SIGNATURE-----
> 


  parent reply	other threads:[~2007-06-05  8:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 16:19 syn DDoS attack solution Bgs
2007-05-31 19:57 ` R. DuFresne
2007-06-01  9:45   ` Bgs
2007-05-31 20:08 ` Ric Messier
2007-06-01  1:20   ` Tony.Ho
2007-06-01  9:44   ` Bgs
2007-06-01 15:01     ` Ric Messier
2007-06-01 15:37       ` Bgs
2007-06-02 19:07         ` R. DuFresne
2007-06-04 14:22           ` Ric Messier
2007-06-04 17:24           ` Martin McKeay
2007-06-04 23:16             ` R. DuFresne
2007-06-05  8:29             ` Bgs [this message]
2007-06-05 14:16               ` Steven M Campbell
2007-06-05 15:22                 ` ..prevention, was: " Arnt Karlsen
     [not found]                   ` <466583F4.8080107@SCampbell.net>
2007-06-05 15:40                     ` Steven M Campbell
2007-06-05 18:34                       ` Arnt Karlsen
2007-06-07 18:41                     ` Martin McKeay
2007-06-08  1:40                       ` Arnt Karlsen
2007-06-12 18:10                       ` Martin McKeay
2007-06-12 22:44                         ` R. DuFresne
2007-06-13 14:24                           ` Martin McKeay
2007-06-13 17:26                             ` Arnt Karlsen
2007-06-13 17:44                               ` Martin McKeay
2007-06-14 19:43                                 ` R. DuFresne
2007-06-14 20:13                                   ` supportnew
2007-06-01 21:34       ` Martijn Lievaart
2007-06-01 21:37         ` Martijn Lievaart
2007-06-01 21:38         ` Ric Messier
2007-06-01 23:09         ` Ethy H. Brito
2007-06-19 18:22         ` R. DuFresne
2007-06-19 22:19           ` Robert Nichols
2007-06-19 23:02             ` Pascal Hambourg
2007-06-21 18:26             ` R. DuFresne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46651F04.9020709@bgs.hu \
    --to=bgs@bgs.hu \
    --cc=kilroy@WasHere.COM \
    --cc=mmckeay@stillsecure.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox