[cifs-protocol] NTCreateAndX with DesiredAccess of 0
Sebastian.Canevari at microsoft.com
Tue May 25 09:07:48 MDT 2010
Thanks for your question.
Someone from my team will be contacting you to work on this inquiry.
Thanks and regards,
From: cifs-protocol-bounces at cifs.org [cifs-protocol-bounces at cifs.org] on behalf of James Peach [jpeach at apple.com]
Sent: Monday, May 24, 2010 11:07 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at samba.org
Subject: [cifs-protocol] NTCreateAndX with DesiredAccess of 0
In MS-FSA 220.127.116.11, the initial parameter validation says that the operation MUST be failed with STATUS_INVALID_PARAMETER if DesiredAccess is zero. This may be true from the perspective of the object store, but it's not correct from the perspective of the SMB client.
The Mac OS X client implements the access(2) system call[*] by sending a SMB_COM_NT_CREATE_ANDX request with a DesiredAccess mask of zero. This causes the server to open a file handle with no access rights, but the SMB_COM_NT_CREATE_ANDX response returns the MaximalAccess which is what the client actually needs. This works with all the Windows versions that we have tested with. I believe that it works because the Windows SMB server implicitly opens the file with a non-zero DesiredAccess mask in order to obtain the necessary information for the SMB_COM_NT_CREATE_ANDX response. Note that providing any value for DesiredAccess might cause the request to fail with STATUS_ACCESS_DENIED, which will not provide the desired functionality.
I'm not sure whether MS-FSA should be updated, but it currently does not describe observable Windows behaviour in this regard.
cifs-protocol mailing list
cifs-protocol at cifs.org
More information about the cifs-protocol