mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Chris Friesen <cfriesen@nortel.com>,
	netdev@vger.kernel.org,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: sunrpc port allocation and IANA reserved list
Date: Wed, 11 Nov 2009 07:14:51 +0900	[thread overview]
Message-ID: <1257891291.3044.50.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1257888720.2834.30.camel@achroite.uk.solarflarecom.com>

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


      parent reply	other threads:[~2009-11-10 22:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 17:43 Chris Friesen
2009-11-10 17:53 ` Ben Hutchings
2009-11-10 18:37   ` Chris Friesen
2009-11-10 18:48     ` Chris Friesen
2009-11-10 20:26     ` Trond Myklebust
2009-11-10 21:06       ` Chris Friesen
2009-11-10 21:17         ` Trond Myklebust
2009-11-10 21:58           ` Trond Myklebust
2009-11-10 21:32         ` Ben Hutchings
2009-11-10 21:34           ` Chuck Lever
2009-11-10 21:42             ` Ben Hutchings
2009-11-10 21:54           ` Chris Friesen
2009-11-10 22:14           ` Trond Myklebust [this message]

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=1257891291.3044.50.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=bhutchings@solarflare.com \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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

all inboxes | Powered by JetHome®