[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1257891291.3044.50.camel@heimdal.trondhjem.org>
Date: Wed, 11 Nov 2009 07:14:51 +0900
From: Trond Myklebust <trond.myklebust@....uio.no>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: Chris Friesen <cfriesen@...tel.com>, netdev@...r.kernel.org,
Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: sunrpc port allocation and IANA reserved list
On Tue, 2009-11-10 at 21:32 +0000, Ben Hutchings wrote:
> On Tue, 2009-11-10 at 15:06 -0600, Chris Friesen wrote:
> > On 11/10/2009 02:26 PM, Trond Myklebust wrote:
> > > Just use /proc/sys/sunrpc/{max,min}_resvport interface to restrict the
> > > range used to a safer one. That's what it is for...
>
> Unless I'm much mistaken, that only affects in-kernel SunRPC users.
There shouldn't be that many non-kernel sunrpc users that require
privileged ports.
The exceptions I can think of are
* the 'mount' program, if you are using the legacy binary mount
interface. Use text mounts instead...
* rpc.statd might also use privileged ports when booting the
system when it needs to notify servers of the reboot. You can
set that port number using the '-o' option.
Others? Do any of the NIS services require it?
Trond
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists