From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nebojsa Miljanovic <neb@alcatel-lucent.com>
Cc: linux-kernel@vger.kernel.org, "Kittlitz,
Edward (Ned)" <nkittlitz@alcatel-lucent.com>,
asweeney@alcatel-lucent.com, "Polhemus,
William (Bart)" <bpolhemus@alcatel-lucent.com>
Subject: Re: SO_REUSEADDR not allowing server and client to use same port
Date: Mon, 17 Mar 2008 17:30:21 +0000 [thread overview]
Message-ID: <20080317173021.28e6fd97@core> (raw)
In-Reply-To: <47DE9FB0.5030801@alcatel-lucent.com>
On Mon, 17 Mar 2008 11:43:28 -0500
Nebojsa Miljanovic <neb@alcatel-lucent.com> wrote:
> Alan,
> thanks. With that additional INFO, I was able to find detailed description of
> this denial of service attack (attached below).
> Just to clarify. Having this port re-use check prevents folks from launching
> this attack as opposed to being victim of it?
Different issue. I can hijack a connection.
Imagine I have a server bound to *.5000, and someone is about to connect.
If on the server box I am able to bind and issue a connect outwards
matching the inbound connection I will get the connection not the server.
next prev parent reply other threads:[~2008-03-17 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 18:15 SO_REUSEADDR not allowing server and client to use same port Nebojsa Miljanovic
2008-02-28 18:30 ` Phil Oester
2008-02-28 20:19 ` Alan Cox
2008-02-28 20:41 ` Willy Tarreau
2008-03-13 19:18 ` Nebojsa Miljanovic
2008-03-15 13:34 ` Alan Cox
2008-03-17 16:43 ` Nebojsa Miljanovic
2008-03-17 17:30 ` Alan Cox [this message]
2008-03-17 18:17 ` Nebojsa Miljanovic
2008-03-18 5:48 ` Willy Tarreau
2008-02-28 20:36 ` Willy Tarreau
2008-02-28 20:44 ` Nebojsa Miljanovic
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=20080317173021.28e6fd97@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=asweeney@alcatel-lucent.com \
--cc=bpolhemus@alcatel-lucent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neb@alcatel-lucent.com \
--cc=nkittlitz@alcatel-lucent.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