netdev - Re: ports beeing reused too fast

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 May 2009 18:52:25 +0300
From:	Octavian Purdila <opurdila@...acom.com>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	netdev@...r.kernel.org, Bill Fink <billfink@...dspring.com>,
	Eric Dumazet <dada1@...mosbay.com>,
	Cosmin Ratiu <cratiu@...acom.com>
Subject: Re: ports beeing reused too fast


> I raised the issue to the original author of the proposed RFC and added
> the issue to the ongoing review of the draft.
>
> There is a suggested workaround using a bitmap but it seems like it would
> be expensive to implement:
>       
> http://ietfreport.isoc.org/all-ids/draft-ananth-tsvwg-timewait-00.txt

OK, I now understand how TW could be an issue here - I didn't realize that we 
could have sockets in TW on the server side.

Since the workaround seems expensive, would it be acceptable to add a new 
sysctl option to disable port randomization?

Thanks,
tavi

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html