netdev - Re: [PATCH net-next] tcp: change source port selection at bind() time

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

Message-ID: <CAL+tcoCYhvB2wB7kxD_ZVEgwMgpLyzzLVZcNjSjDw+NLu7dARQ@mail.gmail.com>
Date: Tue, 20 Aug 2024 17:24:41 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: Kuniyuki Iwashima <kuniyu@...zon.com>
Cc: davem@...emloft.net, dsahern@...nel.org, edumazet@...gle.com, 
	kernelxing@...cent.com, kuba@...nel.org, ncardwell@...gle.com, 
	netdev@...r.kernel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next] tcp: change source port selection at bind() time

On Tue, Aug 20, 2024 at 5:22 PM Jason Xing <kerneljasonxing@...il.com> wrote:
>
> Hello Kuniyuki,
>
> [...]
> > > To be more concise, I would like to state 3 points to see if they are valid:
> > > (1) Extending the option for bind() is the last puzzle of using an
> > > older algorithm for some users. Since we have one in connect(), how
> > > about adding it in bind() to provide for the people favouring the
> > > older algorithm.
> >
> > Why do they want to use bind() to pick a random port in the first place ?
> >
>
> I feel sorry to bother you again.
>
> Interesting thing is that I just found some of my personal records
> that show to me: a lot of applications start active connections using
> bind() to find a proper port in Google :) I'm not the only one :p
> Probably coming up with the new algo selecting odd/even ports is the
> reason/compromise for the bind() and non-bind() users. It gave range/2
> for active flow using bind().
>
> That's what I want to share with you :) Hope it will waste you and
> Eric precious time :)

Sorry, it should be "it won't"...