From: Chuck Lever <chuck.lever@oracle.com>
Date: Thu, 14 Jan 2010 17:24:34 +0000 (-0500)
Subject: libnsm.a: retain CAP_NET_BIND when dropping privileges
X-Git-Tag: nfs-utils-1-2-2-rc7~3
X-Git-Url: https://git.decadent.org.uk/gitweb/?a=commitdiff_plain;h=e2446fda6e7cdb1b9462162b81b0e50fd6efaf56;hp=e2446fda6e7cdb1b9462162b81b0e50fd6efaf56;p=nfs-utils.git

libnsm.a: retain CAP_NET_BIND when dropping privileges

I'm about to switch the order of listener creation and dropping root
privileges.  rpc.statd will drop privileges first, then create its
listeners.  The reason for the new ordering is explained in a
subsequent patch.

However, for non-TI-RPC builds, rpc_init() needs to use a privileged
port to do pmap registrations.  For both TI-RPC and non-TI-RPC builds,
CAP_NET_BIND is required in case the admin requests a privileged
listener port on the statd command line.

So that these requirements are met, nsm_drop_privileges() will now
retain CAP_NET_BIND while dropping root.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---