From: Stephen Hemminger <stephen@networkplumber.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, davem@davemloft.net
Subject: Re: [RFC Patch net-next] inet: introduce a sysctl ip_local_ports_strict_use
Date: Wed, 22 Jul 2015 22:39:04 -0700 [thread overview]
Message-ID: <20150722223904.20ef9011@uryu.home.lan> (raw)
In-Reply-To: <1437610057-13197-1-git-send-email-xiyou.wangcong@gmail.com>
On Wed, 22 Jul 2015 17:07:37 -0700
Cong Wang <xiyou.wangcong@gmail.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.
next prev parent reply other threads:[~2015-07-23 5:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 0:07 [RFC Patch net-next] inet: introduce a sysctl ip_local_ports_strict_use Cong Wang
2015-07-23 5:39 ` Stephen Hemminger [this message]
2015-07-24 20:53 ` Cong Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150722223904.20ef9011@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).