From: Steve Dickson <SteveD@RedHat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/1] Remote calls don't need to use privilege ports
Date: Mon, 5 Feb 2018 14:21:20 -0500 [thread overview]
Message-ID: <6bd33601-2c59-3d19-ece2-878b885c2940@RedHat.com> (raw)
In-Reply-To: <16CF8126-7229-4963-B5D1-2AC16BFC000A@oracle.com>
On 02/05/2018 12:02 PM, Chuck Lever wrote:
> Heya Steve-
>
>> On Feb 5, 2018, at 11:36 AM, Steve Dickson <steved@redhat.com> wrote:
>>
>> Over the weekend I did some experimenting with
>> the remote call code in rpcbind. The code does
>> functionally work but is very antiquated when
>> it comes to the latest NFS versions.
>>
>> Since only UDP sockets are used to do remote calls
>> using the documented interfaces pmap_rmtcall() and callrpc()
>> calls to NFS will fail (actual times out) since UDP is no
>> longer supported.
>>
>> The undocumented interface rpc_call() can be used to
>> call into NFS since the protocol can specified, which
>> also means the PMAPPROC_CALLIT protocol is not used.
>>
>> It turns out privilege port are not needed to make
>> remote calls, at least with my testing.
>
> It's not quite clear what you are claiming here, but
> I'm guessing that what you demonstrated is that the
> CALLIT _listener_ does not have to be privileged?
Right...
>
> I claim that is true for all RPC listeners.
It could be true..
>
>
>> I'm thinking
>> the only reason privilege ports were being uses was
>> a side effect of create_rmtcall_fd() calling
>> svc_tli_create() with an unbound socket.
>
> Privileged listener ports are being created because
> svc_tli_create is using bindresvport when the passed
> in socket is not already bound.
Right... So handing svc_tli_create a bound socket will
cause the bindresvport not to happen.
>
> svc_tli_create should use bind instead, and it needs
> to choose a port higher than 49151.Actual it does when a t_bind structure is passed in.
But more to the point, I thought about changing
svc_tli_create but that would effect all the callers
of the routine which I didn't think was a good idea
for code that is basically not used.
Also, now that libtirpc is the only Linux RPC implementation
(the RPC code has been removed from glibc) I'm a bit
sensitive to changing functionality unless its a
clear bug or security issue.
>
> https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml
Hmm... I have been conveniently ignoring Thorsten's blacklist patch.
Maybe we should take another look at that.
>
>
>> So the following patch simply binds the socket
>> before calling svc_tli_create() which means a
>> non-privilege port will be reserved for remote
>> calls.
>>
>> I'm thinking this is the simplest way to
>> not pollute the privilege port space.
>
> This is going in the right direction, but the problem
> needs to be addressed in svc_tli_create, not in each
> application that calls svc_tli_create.
>
> This is the same issue that Guillem Jover was trying to
> address by making bindresvport skip well-known ports.
>
> In other words: this code in src/svc_generic.c is wrong:
It could be... but the API allows for the bindresvport (or any bind)
to not happen... So changing how it is called I think is
appropriate... Plus its been working this way for a long to so
I'm very resistant to change functionality basically for no reason.
But I do think we should look into bindresvport using a black list
since it is already established in SuSE
steved.
>
> 218 /*
> 219 * If the fd is unbound, try to bind it.
> 220 */
> 221 if (madefd || !__rpc_sockisbound(fd)) {
> 222 if (bindaddr == NULL) {
> 223 if (bindresvport(fd, NULL) < 0) {
> ^^^^^^^^^^^^
>
> 224 memset(&ss, 0, sizeof ss);
> 225 ss.ss_family = si.si_af;
> 226 if (bind(fd, (struct sockaddr *)(void *)&ss,
> 227 (socklen_t)si.si_alen) < 0) {
> 228 warnx(
> 229 "svc_tli_create: could not bind to anonymous port");
> 230 goto freedata;
> 231 }
> 232 }
> 233 listen(fd, SOMAXCONN);
> 234 } else {
> 235 if (bind(fd,
> 236 (struct sockaddr *)bindaddr->addr.buf,
> 237 (socklen_t)si.si_alen) < 0) {
> 238 warnx(
> 239 "svc_tli_create: could not bind to requested address");
> 240 goto freedata;
> 241 }
> 242 listen(fd, (int)bindaddr->qlen);
> 243 }
> 244
> 245 }
>
>
>> Steve Dickson (1):
>> rmtcalls: Don't use privileged ports for remote calls.
>>
>> src/rpcb_svc_com.c | 19 ++++++++++++++++++-
>> 1 file changed, 18 insertions(+), 1 deletion(-)
>
>
> --
> Chuck Lever
>
>
>
next prev parent reply other threads:[~2018-02-05 19:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 16:36 [PATCH 0/1] Remote calls don't need to use privilege ports Steve Dickson
2018-02-05 16:36 ` [PATCH 1/1] rmtcalls: Don't use privileged ports for remote calls Steve Dickson
2018-02-05 17:02 ` [PATCH 0/1] Remote calls don't need to use privilege ports Chuck Lever
2018-02-05 17:09 ` Tom Talpey
2018-02-05 17:11 ` Chuck Lever
2018-02-05 19:46 ` Steve Dickson
2018-02-07 4:35 ` NeilBrown
2018-02-07 16:09 ` Chuck Lever
2018-02-07 21:16 ` NeilBrown
2018-02-07 21:23 ` Chuck Lever
2018-02-07 23:16 ` NeilBrown
2018-02-08 0:13 ` Chuck Lever
2018-02-08 0:45 ` NeilBrown
2018-02-08 0:46 ` Chuck Lever
2018-02-05 19:21 ` Steve Dickson [this message]
2018-02-05 19:47 ` Chuck Lever
2018-02-06 16:37 ` Steve Dickson
2018-02-06 17:34 ` Chuck Lever
2018-02-06 18:22 ` Tom Talpey
2018-02-06 18:36 ` Chuck Lever
2018-02-07 0:15 ` Tom Talpey
2018-02-06 19:00 ` Chuck Lever
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=6bd33601-2c59-3d19-ece2-878b885c2940@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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).