From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Bruce Fields <bfields@citi.umich.edu>,
Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: use of non-privileged ports for MNT and NLM
Date: Tue, 19 Aug 2008 19:44:42 -0400 [thread overview]
Message-ID: <1219189482.7150.6.camel@localhost> (raw)
In-Reply-To: <0CD0CE08-CB11-419A-9AAC-DEB1AC2B26B3@oracle.com>
On Tue, 2008-08-19 at 17:14 -0400, Chuck Lever wrote:
> Working on "resvport" mount option. Question occurred to me:
>
> If I specify "noresvport" on a mount, can the client also use a non-
> privileged port for the initial MNT request, and can it use it for the
> NLM connection as well?
>
> Question applies not just to Linux servers, but servers in general.
> Brief searching on teh internets does not reveal a quick answer. I
> think rpc.mountd will allow a non-privileged port for "insecure"
> exports.
>
> I think the answer is "yes, non-privileged ports can be used for MNT
> and NLM if the server explicitly allows it" but I thought I would open
> this up to the list.
How about a default that tries to connect using an insecure port first,
then falls back to a secure port if the attempt fails?
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2008-08-19 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 21:14 use of non-privileged ports for MNT and NLM Chuck Lever
2008-08-19 21:22 ` J. Bruce Fields
2008-08-19 23:44 ` 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=1219189482.7150.6.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=SteveD@redhat.com \
--cc=bfields@citi.umich.edu \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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 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.