[cifs-protocol] [120071321002570] Clarification on support of SMB_SET_FILE_BASIC_INFO

Jeff McCashland jeffm at microsoft.com
Mon Jul 13 23:01:02 UTC 2020


[Hung-Chun to BCC]

Hi Ronnie,

Thank you for reporting this issue. I will investigate and let you know what I find. 

Best regards,
Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team 
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)
Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300
We value your feedback.  My manager is Natesha Morrison (namorri), +1 (704) 430-4292

-----Original Message-----
From: Hung-Chun Yu <HungChun.Yu at microsoft.com> 
Sent: Monday, July 13, 2020 3:29 PM
To: ronnie sahlberg <ronniesahlberg at gmail.com>
Cc: cifs-protocol at samba.org; support <support at mail.support.microsoft.com>; cifs-protocol at lists.samba.org
Subject: [120071321002570] Clarification on support of SMB_SET_FILE_BASIC_INFO

Hi Ronnie

Thank you for contacting Microsoft Open Specifications Support. We created SR Case 120071321002570 to keep track the issue, do not remove this reference number from the subject line for future reference. One of Engineers will be contacting you regarding the issue shortly.

Hung-Chun Yu
Escalation Engineer
Microsoft Open Specifications

-----Original Message-----
From: ronnie sahlberg <ronniesahlberg at gmail.com> 
Sent: Monday, July 13, 2020 2:10 PM
To: Interoperability Documentation Help <dochelp at microsoft.com>; cifs-protocol at samba.org
Subject: [EXTERNAL] Clarification on support of SMB_SET_FILE_BASIC_INFO

Hi Dochelp,

Reading [MS-CIFS].pdf
In section 3.2.4.13 It mentions TRANS2_SET_PATH_INFORMATION and lists several infolevels and what they are used for.
It specifically lists SMB_SET_FILE_BASIC_INFO.
This works well against all windows servers I have tested with.

However, section 2.2.2.3.4 contradicts this and states that SMB_SET_FILE_BASIC_INFO is NOT supported for TRANS2_SET_PATH_INFORMATION.

Considering 3.2.4.13 and also that it seems to work against windows servers, it 2.2.2.3.4 incorrect?



More information about the cifs-protocol mailing list