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

Date:	Wed, 22 Jul 2015 22:39:04 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Cong Wang <xiyou.wangcong@...il.com>
Cc:	netdev@...r.kernel.org, edumazet@...gle.com, davem@...emloft.net
Subject: Re: [RFC Patch net-next] inet: introduce a sysctl
 ip_local_ports_strict_use

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.

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