From: "David S. Miller" <davem@redhat.com>
To: Gandalf The White <gandalf@digital.net>
Cc: netdev@oss.sgi.com
Subject: Re: Fragmentation Attack
Date: Sat, 7 Feb 2004 09:45:24 -0800 [thread overview]
Message-ID: <20040207094524.495e883d.davem@redhat.com> (raw)
In-Reply-To: <BC4A7E2E.E256%gandalf@digital.net>
On Sat, 07 Feb 2004 11:36:14 -0600
Gandalf The White <gandalf@digital.net> wrote:
> If you want step by step instructions I can provide them.
What makes your DoS interesting is whether the attacker needs
a lot of bandwidth or not. Ie. if he has to be sitting on your
gigabit subnet then the attack isn't interesting. Whereas if he
can eat all of the remote systems cpu cycles just being behind a
cable modem, that's interesting.
Which is it?
Also have you done your cpu utilization tests on something a little
less ancient than a 450mhz system? How fast was the network?
next prev parent reply other threads:[~2004-02-07 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 17:36 Fragmentation Attack Gandalf The White
2004-02-07 17:45 ` David S. Miller [this message]
2004-02-07 18:00 ` Gandalf The White
2004-02-08 20:45 ` David S. Miller
2004-02-08 21:12 ` Gandalf The White
2004-02-08 21:18 ` David S. Miller
2004-02-12 2:20 ` Gandalf The White
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=20040207094524.495e883d.davem@redhat.com \
--to=davem@redhat.com \
--cc=gandalf@digital.net \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).