Parent Lease key empty
smfrench at gmail.com
Mon Mar 2 00:24:09 MST 2015
Was looking at one of Microsoft's leasev2 test case and noticed a
fairly simple test fail with Samba acting strangely.
SMB3 create request with
oplock = lease
and a request for leasev2 (create context)
flags includes SMB2_LEASE_FLAG_PARENT_LEASE_KEY_SET
lease key and parent lease key fields both filled in
SMB3 create response
with R/W lease v2 granted
lease key field filled in, but the parent lease key was zeroed
Even though directory leases are disabled - not echoing that field
back - still seems to violate 126.96.36.199.11 of MS-SMB2 Of course
actually using the parent lease key would probably fail which is ok
but not echoing it back seems illegal.
"If SMB2_LEASE_FLAG_PARENT_LEASE_KEY_SET bit is set in the Flags field
of the request,
ParentLeaseKey MUST be set to the ParentLeaseKey in the request and
SMB2_LEASE_FLAG_PARENT_LEASE_KEY_SET bit MUST be set in the Flags
field of the response."
More information about the samba-technical