Skip to contentSkip to conversation

Question: why only 8 security flavors per export??

DISCUSSION Steve Dickson 3 participants 4 messages Dec 4, 2009 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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.

#2 lore raw
In reply to a message not in the archive
Quoted 11 lines

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

Quoted 7 lines

steved.

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
Quoted 12 lines · Andy Adamson
Quoted 11 lines

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"

Quoted 7 lines

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.

#4 lore raw
In reply to Andy Adamson
Quoted 12 lines · Andy Adamson
Quoted 11 lines

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"

Quoted 8 lines

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.