netdev - Re: [RFC Patch net-next] inet: introduce a sysctl ip_local_ports_strict

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]

Date:	Fri, 24 Jul 2015 13:53:36 -0700
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	Eric Dumazet <edumazet@...gle.com>,
	David Miller <davem@...emloft.net>
Subject: Re: [RFC Patch net-next] inet: introduce a sysctl ip_local_ports_strict_use

On Wed, Jul 22, 2015 at 10:39 PM, Stephen Hemminger
<stephen@...workplumber.org> wrote:
> On Wed, 22 Jul 2015 17:07:37 -0700
> Cong Wang <xiyou.wangcong@...il.com> wrote:
>
>> For a real example, named randomly selects some port to bind() for
>> security concern. (It doesn't use bind(0) to let kernel to select port
>> because it is not random enough, kernel usually just picks the next
>> available.) When running named on a Mesos controlled host, named would
>> silently fail when it binds a port assigned to a Mesos container.
>
> I think named is trying to workaround security issues that were fixed
> 5 years ago in Linux. The kernel does not just pick the next available
> in current code.
>

Good to know that. I will rephrase the changelog.

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