From: "Li.Wang" <Li.Wang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rpcbind: add option to fix port number
Date: Tue, 12 Aug 2014 16:44:18 +0800 [thread overview]
Message-ID: <53E9D3E2.7020101@windriver.com> (raw)
In-Reply-To: <CAJTo0LZW2OdpmevQW+5+j9Vau2M2qUpe+XUEL9aO6b=WS_B5fg@mail.gmail.com>
Hi,
this is a description from customer:
=====
customer's description of the problem:
"
It would seem rcpbind opens a random port.
Clearly not the most simple thing to protect with an ipfilter.
Opening random ports in privileged port range, among them one port
that
identifies itself as pop3s, is not a good practice. Both Ericsson
and our
customers run regular vulnerability assessment tools against our
product,
and this will clearly be seen as a potential problem. Furthermore,
we will
not be able to filter the ports, since they are random, and neither
will we
be able to provide decent answers to our customers. To summarize: this
should be taken care of, ie fix rpcbind so that it uses a non
random port
and/or to bind to a specific interface.
=====
Thanks,
LiWang.
On 08/12/2014 04:41 PM, Burton, Ross wrote:
> On 12 August 2014 08:20, Li Wang <li.wang@windriver.com> wrote:
>> fix a random port to offer customer an option for select.
> I'm curious as to why this is needed.
>
> Ross
next prev parent reply other threads:[~2014-08-12 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 6:25 [PATCH] rpcbind: add option to fix port number Li Wang
2014-08-12 7:20 ` Li Wang
2014-08-12 8:10 ` Li.Wang
2014-08-12 8:11 ` Li Wang
2014-08-12 8:41 ` Burton, Ross
2014-08-12 8:44 ` Li.Wang [this message]
2014-09-05 15:24 ` Burton, Ross
2014-09-09 8:33 ` Li.Wang
2014-08-12 8:48 ` Burton, Ross
2014-08-12 9:03 ` Li 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=53E9D3E2.7020101@windriver.com \
--to=li.wang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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