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: <CANn89iJUM86t-hYC_W5KS1gn+NOFP4zoaS+99Cpvx+tOO=mxoQ@mail.gmail.com>
Date: Tue, 8 Jul 2025 02:35:35 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Jakub Sitnicki <jakub@...udflare.com>
Cc: Paolo Abeni <pabeni@...hat.com>, "David S. Miller" <davem@...emloft.net>, 
	Jakub Kicinski <kuba@...nel.org>, Neal Cardwell <ncardwell@...gle.com>, 
	Kuniyuki Iwashima <kuniyu@...gle.com>, netdev@...r.kernel.org, kernel-team@...udflare.com, 
	Lee Valentine <lvalentine@...udflare.com>
Subject: Re: [PATCH net-next v2 1/2] tcp: Consider every port when connecting
 with IP_LOCAL_PORT_RANGE

On Tue, Jul 8, 2025 at 2:13 AM Jakub Sitnicki <jakub@...udflare.com> wrote:

> I was wondering what the maintainers' outlook on this change is:
>
> Does this sound acceptable?
> Or should we start looking in a different direction?
>


Long weekend, and a big number of submissions while we were away.

Let me take a look.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ