From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: Mohit Katiyar <katiyar.mohit@gmail.com>,
linux-kernel@vger.kernel.org,
Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: NFS inconsistent behaviour
Date: Wed, 18 Oct 2006 14:37:12 -0400 [thread overview]
Message-ID: <1161196632.6095.94.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1161194229.6095.81.camel@lade.trondhjem.org>
On Wed, 2006-10-18 at 13:57 -0400, Trond Myklebust wrote:
> Note also that you _can_ change the range of ports used by the NFS
> client itself at least. Just edit /proc/sys/sunrpc/{min,max}_resvport.
> On the server side, you can use the 'insecure' option in order to allow
> mounts that originate from non-privileged ports (i.e. port > 1024).
> If you are using strong authentication (for instance RPCSEC_GSS/krb5)
> then that actually makes a lot of sense, since the only reason for the
> privileged port requirement was to disallow unprivileged NFS clients.
Oops... Something got lost there. That last sentence should read
...since the only reason for the privileged port requirement was
to disallow unprivileged NFS clients that could be used to spoof
other user identities via the weak AUTH_SYS authentication.
Cheers,
Trond
next prev parent reply other threads:[~2006-10-18 18:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A93BD15112CD05479B1CD204F7F1D4730513DB@exch-04.noida.hcltech.com>
2006-10-16 7:13 ` Mohit Katiyar
2006-10-16 8:46 ` Frank van Maarseveen
2006-10-16 9:35 ` Mohit Katiyar
2006-10-16 9:39 ` Frank van Maarseveen
2006-10-18 1:22 ` Mohit Katiyar
2006-10-18 6:39 ` Frank van Maarseveen
2006-10-18 17:57 ` Trond Myklebust
2006-10-18 18:37 ` Trond Myklebust [this message]
2006-10-18 18:38 ` Frank van Maarseveen
2006-10-18 19:26 ` Trond Myklebust
2006-10-18 20:09 ` [NFS] " Frank van Maarseveen
2006-10-18 20:17 ` Chuck Lever
2006-10-18 20:44 ` Trond Myklebust
2006-10-19 12:11 ` Alan Cox
2006-10-19 1:53 ` Mohit Katiyar
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=1161196632.6095.94.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=frankvm@frankvm.com \
--cc=katiyar.mohit@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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®