public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
	Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH 0/2] Make libtirpc work with old style portmapper
Date: Mon, 30 Aug 2010 18:19:18 +0200	[thread overview]
Message-ID: <201008301819.18773.okir@suse.de> (raw)
In-Reply-To: <30F1122D-13FB-4B6B-9BA2-99112306581F@oracle.com>

On Monday 30 August 2010 17:59:18 Chuck Lever wrote:
> I worried at the time that this might introduce a security weakness, since,
>  after all, the rpcbind SET operation goes over AF_UNIX, which is
>  authenticated, but pmap uses sockets with privileged ports to detect
>  authorized users.  I see that your logic uses the pmap SET/UNSET calls by
>  default. This bypasses AF_UNIX completely in pretty much all local cases,

That is admittedly a problem, at least for services not running as root.
For services running as root, there's no change in behavior when talking
to rpcbind - the registration will be owned by the superuser in both
cases, because instead of checking the AF_LOCAL credentials for uid 0 it
will check for a privileged source port. I agree though, that this part of
the patch doesn't leave me totally at ease.

>  which changes the behavior of rpcb_set() and rpcb_unset(), and could break
>  the local rpcbind security model.  It might be better to use
>  pmap_setunset() only when local_rpcb() fails.

If it helps, I could do the old PMAP calls as a fallback rather than
trying these by default, agreed. Let me see what I can come up with
tomorrow.

> Another minor problem I think I remember is that if libtirpc is used on a
>  system (perhaps because it is statically linked with said ISV RPC-enabled
>  application) that does not have /etc/netconfig installed, the transport
>  creation logic in rpcb_clnt.c simply doesn't work.

Well, but that's something that's fixed easily - we can always tell
such customer to install an /etc/netconfig on their system.

Olaf
-- 
Neo didn't bring down the Matrix. SOA did. (soafacts.com)
--------------------------------------------
Olaf Kirch - Director Server (okir@novell.com)
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2010-08-30 16:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 13:03 [PATCH 0/2] Make libtirpc work with old style portmapper Olaf Kirch
2010-08-30 13:04 ` [PATCH 1/2] Introduce new helper function getpmaphandle Olaf Kirch
2010-08-30 13:04   ` [PATCH 2/2] " Olaf Kirch
2010-08-30 15:59 ` [PATCH 0/2] Make libtirpc work with old style portmapper Chuck Lever
2010-08-30 16:19   ` Olaf Kirch [this message]
2010-08-30 23:48     ` Chuck Lever
2010-09-07 11:27       ` Olaf Kirch
2010-09-07 15:36         ` Chuck Lever
2010-09-07 20:58           ` Olaf Kirch
2010-09-07 21:15             ` 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=201008301819.18773.okir@suse.de \
    --to=okir@suse.de \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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