netdev - inet_hash_connect: source port allocation

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-next>] [day] [month] [year] [list]

Date:	Mon, 29 Nov 2010 17:04:02 +0000
From:	John Haxby <john.haxby@...cle.com>
To:	NetDev <netdev@...r.kernel.org>
Subject: inet_hash_connect: source port allocation

Hello,

Please forgive me if this is a stupid question, but is there any 
particular reason why the source port allocation in 
__inet_hash_connect() shouldn't use the same random allocation that 
inet_csk_get_port() uses?  The latter, of course, is used when bind() 
doesn't specify a source port but the implicit "bind" for a connect() 
gets its port allocated by __inet_hash_connect().

jch
--
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