login
Header Space

 
 

Re: SO_REUSEADDR not allowing server and client to use same port

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Alan Cox <alan@...>
Cc: Nebojsa Miljanovic <neb@...>, <linux-kernel@...>, Kittlitz, Edward (Ned) <nkittlitz@...>, <asweeney@...>, Polhemus, William (Bart) <bpolhemus@...>
Date: Thursday, February 28, 2008 - 4:41 pm

On Thu, Feb 28, 2008 at 08:19:26PM +0000, Alan Cox wrote:

exactly. That's why I think that requiring the server to explicitly allow
socket reuse is mandatory. On another side of the problem, I really think
that we should make the simultaneous connect configurable. I've been patching
all of my own 2.4 kernels for a while to add a config option to turn it off
because there is a real security issue with this on. At least for mainline,
it should be a sysctl. No stateful firewall I know supports the feature, so
legitimate uses of this feature are likely very very small.

Willy
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
SO_REUSEADDR not allowing server and client to use same port, Nebojsa Miljanovic, (Thu Feb 28, 2:15 pm)
Re: SO_REUSEADDR not allowing server and client to use same ..., Willy Tarreau, (Thu Feb 28, 4:41 pm)
speck-geostationary