Dear Trond, > ... what you are proposing is a potential security problem. Yes, definitely: if ever such options were implemented, then potential users should evaluate whether using them (or not using them) introduced a security vulnerability. That said... NFS security traditionally depended on UIDs and GIDs being "in sync" between the server and the clients. My proposal simply would enforce all GIDs to be "in sync" with the UID, as per server view; most often that would be a no-op (except for accesses by setuid or setgid apps). Seems that kerberos has no concept of groups but only of "principals" which are somewhat like UIDs. My proposal would bring NFSv3 in line with the NFSv4+krb model of "only the UID matters". Cheers, Paul Paul Szabo psz@xxxxxxxxxxxxxxxxx http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of Sydney Australia -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
