All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andy Adamson <andros@netapp.com>
Cc: Steve Dickson <SteveD@redhat.com>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: Question: why only 8 security flavors per export??
Date: Fri, 4 Dec 2009 13:10:41 -0500	[thread overview]
Message-ID: <20091204181041.GA18525@fieldses.org> (raw)
In-Reply-To: <68742FB7-C923-4219-909F-F47B992584C6@netapp.com>

On Fri, Dec 04, 2009 at 12:08:30PM -0500, Andy Adamson wrote:
>
>
>> Hello,
>>
>> Why are only 8 (SECFLAVOR_COUNT) security flavors allow
>> per export when 13 security flavors are supported
>> (see flav_map[] in  nfs/exports.c)?
>>
>> I'm trying to create an export that supports all possible
>> security flavors and its erroring out with "mountd: more than
>> 8 security flavors on an export"
>
> SPKM3 drafts have expired, and the LIPKEY RFC is based on SPKM3 and was 
> never implemented. The SPKM3 implementation was used for  
> experimentation, but never in production anywhere and should probably be 
> removed from the kernel. So in reality, the list of all possible  
> security flavors is:
>
> AUTH_NONE, AUTH_NULL, AUTH_SYS, AUTH_UNIX, krb5, krb5i and krb5p.

Yeah.  Until there's some practical use for more than 8 simultaneous
flavors, I don't think we care about this limit.

--b.

  reply	other threads:[~2009-12-04 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 16:11 Question: why only 8 security flavors per export?? Steve Dickson
     [not found] ` <4B1934A7.90801-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-12-04 17:08   ` Andy Adamson
2009-12-04 18:10     ` J. Bruce Fields [this message]
2009-12-04 18:30     ` Steve Dickson

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=20091204181041.GA18525@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=andros@netapp.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.