From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Support parsing multiple security flavors
Date: Tue, 24 Jun 2008 16:51:01 -0400 [thread overview]
Message-ID: <1214340661.7156.54.camel@localhost> (raw)
In-Reply-To: <20080624202913.3366.44867.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
On Tue, 2008-06-24 at 16:33 -0400, Chuck Lever wrote:
> Hi Trond-
>
> The following four patches implement support in the NFS client's mount option
> parser for multiple security flavors via "sec=flavor:flavor:flavor:..." This
> replicates similar support in the legacy (non text-based) mount.nfs command.
>
> Since the NFS client itself doesn't support multiple security flavors at the
> moment, these have been build-tested only.
>
> Please consider them for 2.6.27.
Are you planning to add support for security negotiation or multiple
security flavours in time for 2.6.27? If not, I suggest we delay this
until such functionality exists.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2008-06-24 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 20:33 [PATCH 0/4] Support parsing multiple security flavors Chuck Lever
[not found] ` <20080624202913.3366.44867.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-24 20:33 ` [PATCH 1/4] NFS: Refactor logic for parsing NFS security flavor mount options Chuck Lever
2008-06-24 20:33 ` [PATCH 2/4] NFS: Set security flavor default for NFSv2/3 mounts like other defaults Chuck Lever
[not found] ` <20080624203345.3366.31456.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-26 19:48 ` Trond Myklebust
2008-06-26 20:53 ` Chuck Lever
2008-06-24 20:33 ` [PATCH 3/4] NFS4: Set security flavor default for NFSv4 " Chuck Lever
2008-06-24 20:34 ` [PATCH 4/4] NFS: text-based mounts should support multiple security flavors Chuck Lever
2008-06-24 20:51 ` 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=1214340661.7156.54.camel@localhost \
--to=trond.myklebust@netapp.com \
--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.