From: Pavel Machek <pavel@suse.cz>
To: jamal <hadi@cyberus.ca>, Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: ECN: Clearing the air
Date: Sun, 28 Jan 2001 22:55:30 +0100 [thread overview]
Message-ID: <20010128225530.A1300@bug.ucw.cz> (raw)
In-Reply-To: <20010128150813.A1595@metastasis.f00f.org> <Pine.GSO.4.30.0101272110470.24762-100000@shell.cyberus.ca>
In-Reply-To: <Pine.GSO.4.30.0101272110470.24762-100000@shell.cyberus.ca>; from jamal on Sat, Jan 27, 2001 at 09:15:48PM -0500
Hi!
> > suggested blocking ECN. Article at:
> >
> > http://www.securityfocus.com/frames/?focus=ids&content=/focus/ids/articles/portscan.html
> >
> > the site is now ATM -- can someone briefly explain the logic in
> > blocking it?
>
> It is Queso they quoted not nmap, sorry -- same thing.
> The idea is to "detect" port scanners.
> Queso sets the two TCP reserved bits in the SYN (now allocated for ECN).
> Some OSes reflect that back in the SYN-ACK (Linux < 2.0.2? for example
> was such a culprit).
Does not that mean that Linux 2.0.10 mistakenly announces it is ECN
capable when offered ECN connection?
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.30.0101271809070.24762-100000@shell.cyberus.ca>
2001-01-28 0:23 ` ECN: Clearing the air jamal
2001-01-28 2:08 ` Chris Wedgwood
2001-01-28 2:15 ` jamal
2001-01-28 21:55 ` Pavel Machek [this message]
2001-01-29 16:21 ` Walter Hofmann
2001-01-30 2:11 ` jamal
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=20010128225530.A1300@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=cw@f00f.org \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.