Found by Gordon Ross (from samba-technical): Can anyone explain why this padding check is here? libcli/smb/smb2cli_query_info.c : 157 if (output_buffer_length < dyn_len) { tevent_req_nterror( req, NT_STATUS_INVALID_NETWORK_RESPONSE); return; } That's demanding the that query response data is padded out to fill the (padded out) length of the SMB2 response. As far as I can tell, the spec. does not require that, and the Samba client appears to be the only one we've run across that insists on this padding. To clarify, we pad the (outer) SMB2 response to 8 bytes as required by MS-SMB2, but we don't currently pad out the query info response data contained therein. Did I miss something in one of the specs?
Created attachment 10322 [details] git-am fix for 4.1.next, 4.0.next. Patch cherry-picked that went into master. Jeremy.
Karolin, please merge. Thanks!
Pushed to autobuild-v4-[0|1|2]-test. Jeremy, please check if it's really appropriate for 4.2 also. Thanks!
(In reply to Karolin Seeger from comment #3) > Pushed to autobuild-v4-[0|1|2]-test. > > Jeremy, please check if it's really appropriate for 4.2 also. Thanks! Yes, it needs to be in 4.2.
(In reply to Jeremy Allison from comment #4) Thanks!
Pushed to all three branches. Closing out bug report. Thanks!