Question: why only 8 security flavors per export??

Question: why only 8 security flavors per export??

[Steve Dickson]

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"

steved.

Re: Question: why only 8 security flavors per export??

[Andy Adamson]

> 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.

-->Andy
>
> steved.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs"  
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Question: why only 8 security flavors per export??

[J. Bruce Fields]

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.

Re: Question: why only 8 security flavors per export??

[Steve Dickson]

On 12/04/2009 12:08 PM, 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.
> 
Ok... thanks... 

steved.