netdev - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1291051560.3435.1198.camel@edumazet-laptop>
Date:	Mon, 29 Nov 2010 18:26:00 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	John Haxby <john.haxby@...cle.com>
Cc:	NetDev <netdev@...r.kernel.org>
Subject: Re: inet_hash_connect: source port allocation

Le lundi 29 novembre 2010 à 17:04 +0000, John Haxby a écrit :
> 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

autobind vs bind

bind() gives more information, like local address (if any)

autobind(), we dont know local address, it'll be chose later by routing.



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