On 04/04/2011 11:14 AM, J. Bruce Fields wrote: > On Mon, Apr 04, 2011 at 09:43:24AM -0400, Bryan Schumaker wrote: >> Hi Bruce, >> >> I'm looking at secinfo_no_name on the client. RFC 5661 says to says to send PUTROOTFH followed by SECINFO_NO_NAME in the same compound and to use SECINFO_STYLE4_CURRENT_FH. My compound is: SEQUENCE, PUTROOTFH, SECINFO_NO_NAME. The server processes up to the PUTROOTFH, and then returns with NFS4ERR_WRONGSEC. >> >> Am I doing something wrong? Is this a server problem? > > Could be; is the compound is being sent with a security flavor that > *isn't* permitted on the root export? > > If so I believe the compound should have succeeded--the server needs > some special exception there that we may have left out.... The root export is set up with sec=null and my compound is using auth_unix. > > --b. > -- > 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 -- 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
