Steve Ruiz wrote: > Now running into a new issue with this. It seems that the linux host is > using auth_none for all subsequent communication on this system, so things > like creating files as a non-root user end up with that file being owned by > root. Any ideas on sharing the export in another way so that doesn't happen? > I know this sounds like a linux issue but wondering if there's anything I can > do on the solaris side to prevent it. >
Steve, I believe that newer Linux client mount and nfs might take care of this problem. I.e., I think it won't use AUTH_NONE. We've been working with the Linux NFS maintainers to fix issues like this one. You might recap why the Linux client is using AUTH_NONE and send it out to linux-nfs at vger.kernel.org. You can feel free to CC me on the message and I'll follow up as needed. But from the server side, I think you are screwed at a protocol level. If AUTH_NONE is used, then the anonymous uid is used for permissions. You have it set to 0, to allow clients to be root, but even if you take that off and use the root access list, you will come across as nobody. You really, really do not want to be communicating with AUTH_NONE here, which ends up being a client issue. Thanks, Tom
