public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: Breno Silva <brenosp@brasilsec.com.br>,
	Stan Bubrouski <stan@ccs.neu.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: Size of Tasks during ddos
Date: Thu, 11 Sep 2003 10:28:50 -0700	[thread overview]
Message-ID: <20030911172850.GC18399@matchmail.com> (raw)
In-Reply-To: <200309111419.h8BEJbSo010948@turing-police.cc.vt.edu>

On Thu, Sep 11, 2003 at 10:19:37AM -0400, Valdis.Kletnieks@vt.edu wrote:
> The answer will differ depending whether (for example) you're being ICMP
> flooded, SYN-flooded, hit with a mass of HTTP 'GET /' commands, hit with a mass
> of HTTP commands that invoke a resource-intensive CGI like a database search,
> and so on.
> 
> We'd really need to know what the traffic involved in the DDoS is in order to
> be able to comment on memory usage.

True, but it's not a ddos unless they do everything they can to disable the
target system.  Sure they could just flood your net pipe, but why do that
when you could have fewer senders and completely kill the box for a long
time while it tries to process all of your requests (assuming you're running
services accessable from the net).

  parent reply	other threads:[~2003-09-11 17:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-11 22:34 Size of Tasks during ddos Breno
2003-09-11  0:27 ` [OT] " Joshua Kwan
2003-09-11  2:10   ` Stan Bubrouski
2003-09-11 12:33     ` Breno Silva
2003-09-11 14:19       ` Valdis.Kletnieks
2003-09-11 17:27         ` Breno
2003-09-11 18:41           ` Alan Cox
2003-09-11 21:23             ` Mike Fedyk
2003-09-11 21:26               ` Alan Cox
2003-09-11 21:30                 ` Mike Fedyk
2003-09-11 21:40                   ` Alan Cox
2003-09-11 22:15               ` Arjan van de Ven
     [not found]             ` <002801c3789e$7a665ac0$9f0210ac@forumci.com.br>
     [not found]               ` <1063312815.3886.0.camel@dhcp23.swansea.linux.org.uk>
2003-10-11 22:09                 ` Breno
2003-09-11 22:14                   ` Alan Cox
2003-09-12 15:36                   ` insecure
2003-09-12 17:56                     ` Mail header times was: " Mike Fedyk
2003-09-11 17:28         ` Mike Fedyk [this message]
2003-09-23 21:08   ` [OT] " bill davidsen
     [not found] <um6w.4VI.5@gated-at.bofh.it>
     [not found] ` <unFh.7rt.7@gated-at.bofh.it>
     [not found]   ` <upe3.1uM.3@gated-at.bofh.it>
     [not found]     ` <uyU4.7Sz.9@gated-at.bofh.it>
     [not found]       ` <uACA.2fO.3@gated-at.bofh.it>
     [not found]         ` <uDTR.7A2.35@gated-at.bofh.it>
     [not found]           ` <uEGe.uJ.21@gated-at.bofh.it>
     [not found]             ` <uHb2.76X.15@gated-at.bofh.it>
     [not found]               ` <uHb6.76X.29@gated-at.bofh.it>
     [not found]                 ` <uHkC.7kf.7@gated-at.bofh.it>
     [not found]                   ` <uHuj.7yv.9@gated-at.bofh.it>
2003-09-11 23:08                     ` Andi Kleen

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=20030911172850.GC18399@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=brenosp@brasilsec.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stan@ccs.neu.edu \
    /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