All of lore.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: Tue, 7 Sep 2010 22:58:21 +0200	[thread overview]
Message-ID: <201009072258.22044.okir@suse.de> (raw)
In-Reply-To: <F1D592E6-35AD-45DA-B69E-044D59500DFB@oracle.com>

On Tuesday 07 September 2010 17:36:58 Chuck Lever wrote:
> Probably not a bad idea.  But I thought this was a problem for applications
>  that are calling rpcb_{un,}set(3t), not apps that are invoking the legacy
>  variants.  How does this new patch address the problem?

No, it's a problem with legacy apps calling pmap_set/unset. They simply
stop working if you use pmap_set + libtirpc + portmap.

> What happens if you try the other way around: try the AF_UNIX mechanism
>  first, then the legacy mechanism?  It's arguable that any application
>  calling the pmap_{un,}set(3t) interface would likely expect the old
>  behavior anyway, but could probably benefit from the additional security
>  if rpcbind, rather than portmap, is running locally.

I don't think apps coded to the old pmap_* interface will benefit
in any way from the new security model. These services expect a
root/non-root split of privilege, and that's what they get with
PMAP_SET/UNSET, no matter whether they talk to rpcbind or portmap.

>   1.  rpcb_{un,}set(3t) need to work whether rpcbind or portmapper are
>  running 2.  pmap_{un,}set(3t) should still invoke rpcb_{un,}set(3t) under
>  the covers to ensure they get advanced security when available
> 
> This is because you can build legacy apps against libtirpc (which want
>  robust pmap_{un,}set(3t) no matter which portmapper is running), but you
>  can also construct TI-RPC enabled apps that may be running on a system
>  with only portmap (which want robust rpcb_{un,}set(3t)).  So I think you
>  have to fix both APIs.

The latter is a problem indeed, and I guess we need to fix it as well.
The one that I wanted to address first and foremost is applications
using the legacy API

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-09-07 20:58 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
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 [this message]
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=201009072258.22044.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.