From: Taylor Grant <gtaylor@riverviewtech.net>
To: Chris Brenton <cbrenton@chrisbrenton.org>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: TCP packets with RST flag set but **not** ACK flag OK??
Date: Mon, 11 Apr 2005 23:01:31 -0500 [thread overview]
Message-ID: <425B481B.7070108@riverviewtech.net> (raw)
In-Reply-To: <1113278818.2151.87.camel@grendel>
> If I follow what you are saying here, the concern is the returning ICMP
> host unreachables may be used as part of a DoS. Is this correct?
Yes, you are following me there.
> If so, the concern is pretty minimal. Packet size is small, only 56
> bytes in size, so bandwidth utilization is small. Unsolicited ICMP
> errors are going to be quickly discarded by the receiving system, so its
> not going to cause much of a CPU hit on the target. Unfortunately there
> are far too many other ways of performing a DoS that would be much more
> effective and efficient.
*nod* I'm not saying that it's one of the most efficient ways to DDoS someone, but I am saying that it is a way and some institutions politically decide that they would rather DROP packets than possibly participate in a DDoS against someone else.
> Ya, geek stuff is cool. :D
It has gotten me in to trouble too. I tend to spend too much time working on geek stuff. Oh, well I had fun doing it.
Grant. . . .
next prev parent reply other threads:[~2005-04-12 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 19:18 TCP packets with RST flag set but **not** ACK flag OK?? Christian Seberino
2005-04-11 19:49 ` Chris Brenton
2005-04-11 21:57 ` Taylor, Grant
2005-04-12 0:36 ` Chris Brenton
2005-04-12 2:32 ` Grant Taylor
2005-04-12 4:06 ` Chris Brenton
2005-04-12 4:01 ` Taylor Grant [this message]
2005-04-12 7:24 ` Taylor Grant
2005-04-12 14:41 ` Chris Brenton
2005-04-12 4:22 ` Taylor Grant
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=425B481B.7070108@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=cbrenton@chrisbrenton.org \
--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