Re: [nfsv4] AUTH_GSS for Callbacks

Next message: Nicolas Williams: "Re: [nfsv4] more on gss authentication for callback"
Previous message: Mike Eisler: "RE: [nfsv4] more on gss authentication for callback"
In reply to: wurzl, mario: "RE: [nfsv4] AUTH_GSS for Callbacks"
Next in thread: Nicolas Williams: "Re: [nfsv4] AUTH_GSS for Callbacks"

mike@eisler.com

Message-ID: <3FA19693.7000507@eisler.com>
From: Mike Eisler <mike@eisler.com>
Subject: Re: [nfsv4] AUTH_GSS for Callbacks
Date: Thu, 30 Oct 2003 14:54:11 -0800

wurzl, mario wrote:

> Introducing a new protocol that increases client administration costs, is
> probably the most effective way to discourage deployment, and send the
> protocol to the same basket with other great but unmanageable ideas, like
> OSI.

That Kevin and you keep bringing up this issue suggests that
you are unhappy with using AUTH_NONE for SETCLIENTID, which solves the
ease of administration issue. So what is your proposal for something that
is more secure than using AUTH_NONE and still has the level of
ease of admin you want?

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4