From: Ed L Cashin <ecashin@terry.uga.edu>
To: linux-kernel@vger.kernel.org (Linux kernel)
Subject: test SYN cookies (was Re: SYN cookies security bugfix?)
Date: 08 Nov 2001 17:00:30 -0500 [thread overview]
Message-ID: <m3y9lgkjnl.fsf@terry.uga.edu> (raw)
In-Reply-To: <E161oM3-0007Xm-00@the-village.bc.nu>
In-Reply-To: <E161oM3-0007Xm-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > I received a forwarded message from SuSE regarding a security vulnerability
> > with respect to randomization of the ISN for SYN cookies - or something to
> > that effect. I have not been able to find the patch which addresses this
> > problem; if anyone can point me towards it, I would be appreciative.
>
> Its fixed in 2.2.20, you can grab the 2.2 patch from there
What is a good way to test SYN cookies? I can induce a three-second
delay (on victim host V) before new TCP connections are accepted by
sending a burst of 2000 SYN packets (from attacker A), where V is
running a 2.2.14 or 2.2.17 kernel. During the three seconds ICMP echo
requests from A to V are being answered.
Turning on SYN cookies after /proc is mounted does not affect the
three-second pause, though, so I figure that either the pause is not
on account of a full half-open connection queue or SYN cookies are not
working.
--
--Ed Cashin PGP public key:
ecashin@terry.uga.edu http://www.terry.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~2001-11-08 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 5:20 SYN cookies security bugfix? B. James Phillippe
2001-11-08 8:32 ` Gianni Tedesco
2001-11-08 12:32 ` Alan Cox
2001-11-08 22:00 ` Ed L Cashin [this message]
2001-11-10 22:04 ` test SYN cookies (was Re: SYN cookies security bugfix?) Ed L Cashin
2001-11-10 22:34 ` Alan Cox
2001-11-11 5:17 ` Ed L Cashin
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=m3y9lgkjnl.fsf@terry.uga.edu \
--to=ecashin@terry.uga.edu \
--cc=linux-kernel@vger.kernel.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