Re: [PATCH] nfs-utils: Handle authentication flavour order properly

[Peter Staubach <staubach@redhat.com>]

bc Wong wrote:
> On Fri, Mar 7, 2008 at 10:29 AM, Peter Staubach <staubach@redhat.com> wrote:
>   
>>  Actually, NFS servers that support AUTH_NONE, map the uid and gid to the
>>  anonymous uid and gids for access to file systems which are exported
>>  AUTH_NONE.  It doesn't seem to matter what authentication flavor that
>>  the client uses.
>>
>>        ps
>>     
>
> Hi Peter,
>
> My concern is that a server supports both AUTH_SYS and AUTH_NONE,
> where AUTH_SYS would give you the regular access, and AUTH_NONE
> would give the anon access as you described, which is typically a
> degraded read-only view. Therefore it's bad for the client to choose
> AUTH_NONE in this case, especially since the server presents
> AUTH_SYS *before* AUTH_NONE.
>
> I'll test more with AUTH_NONE on Solaris. Is there any specific setup
> you'd like me to verify?

Do you know of any client NFS implementations that can actually generate
requests with AUTH_NONE as the authentication flavor?  Which server
implementation supports the mode that you described?

As far as I know, all servers, which support exporting with AUTH_NONE,
always map the incoming uid and gid(s) to the anonymous uid and gid when
they process the request for a file system which is exported with AUTH_NONE.
It doesn't seem to matter what the incoming authentication flavor was.

    Thanx...

       ps