From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Mike Waychison <Michael.Waychison@sun.com>,
Charles Lever <Charles.Lever@netapp.com>,
nfs@lists.sourceforge.net
Subject: Re: [PATCH] xprt sharing (was Re: xprt_bindresvport)
Date: Thu, 9 Dec 2004 14:44:41 +0100 [thread overview]
Message-ID: <20041209134441.GB11998@suse.de> (raw)
In-Reply-To: <1102599415.24133.34.camel@lade.trondhjem.org>
On Thu, Dec 09, 2004 at 08:36:55AM -0500, Trond Myklebust wrote:
> > Shouldn't we allow NFS mounts to use non-privileged ports? Many
> > environments don't really care about the "security" provided by privileged
> > ports, but would be more than happy if they can run with a few hundred
> > NFS mounts
>
> Most AUTH_SYS based models still require it, however I agree that use of
> strong security makes the privileged port totally redundant.
The Linux auth_sys works fine with unprivileged ports if you allow it to;
so why shouldn't we make that configurable on the client too? It'd sure
help some installations who for some reason or other habe an excessive
number of exported file systems (see .sig below :).
Olaf
--
Olaf Kirch | Things that make Monday morning interesting, #2:
okir@suse.de | "We have 8,000 NFS mount points, why do we keep
---------------+ running out of privileged ports?"
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-12-09 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 14:33 xprt_bindresvport Lever, Charles
2004-12-08 18:17 ` [PATCH] xprt sharing (was Re: xprt_bindresvport) Mike Waychison
2004-12-09 11:31 ` Olaf Kirch
2004-12-09 13:36 ` Trond Myklebust
2004-12-09 13:44 ` Olaf Kirch [this message]
2004-12-09 16:20 ` Trond Myklebust
2004-12-09 19:34 ` Dan Stromberg
2004-12-09 21:33 ` Trond Myklebust
2004-12-09 22:29 ` Dan Stromberg
2004-12-09 11:01 ` xprt_bindresvport Olaf Kirch
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 19:08 [PATCH] xprt sharing (was Re: xprt_bindresvport) Lever, Charles
2004-12-08 21:58 ` Mike Waychison
2004-12-09 11:22 ` Olaf Kirch
2004-12-09 13:33 ` Trond Myklebust
2004-12-09 13:41 ` Olaf Kirch
2004-12-08 22:00 Lever, Charles
2004-12-09 8:54 Peter Åstrand
2004-12-09 11:14 ` Olaf Kirch
2004-12-09 14:03 Lever, Charles
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=20041209134441.GB11998@suse.de \
--to=okir@suse.de \
--cc=Charles.Lever@netapp.com \
--cc=Michael.Waychison@sun.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.