mirror of
https://github.com/samba-team/samba.git
synced 2024-12-25 23:21:54 +03:00
3b1b2e6046
This test checks the SMB 2.1.0 behaviour of lock sequence checking, which is only turned on for resilient handles. Even Windows Server 2019 only implements lock sequence checking only for resilient and persistent handles as a server. While its client side uses lock sequence checking if it negotiated multichannel with the server. Hopefully this will be fixed in future Windows versions. Make it clear that this test is supposed to pass against the legacy Windows servers which violate the specification: [MS-SMB2] 3.3.5.14 Receiving an SMB2 LOCK Request ... ... if Open.IsResilient or Open.IsDurable or Open.IsPersistent is TRUE or if Connection.Dialect belongs to the SMB 3.x dialect family and Connection.ServerCapabilities includes SMB2_GLOBAL_CAP_MULTI_CHANNEL bit, the server SHOULD<314> perform lock sequence verification ... ... <314> Section 3.3.5.14: Windows 7 and Windows Server 2008 R2 perform lock sequence verification only when Open.IsResilient is TRUE. Windows 8 through Windows 10 v1909 and Windows Server 2012 through Windows Server v1909 perform lock sequence verification only when Open.IsResilient or Open.IsPersistent is TRUE. Note <314> also applies to all versions (at least) up to Windows Server v2004. Hopefully this will be fixed in future Windows versions and they will avoid Note <314>. Signed-off-by: Stefan Metzmacher <metze@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org> |
||
---|---|---|
.. | ||
auth | ||
build/pasn1 | ||
cldap_server | ||
client | ||
cluster | ||
dns_server | ||
dsdb | ||
echo_server | ||
heimdal | ||
heimdal_build | ||
include | ||
kdc | ||
ldap_server | ||
lib | ||
libcli | ||
libnet | ||
librpc | ||
nbt_server | ||
ntp_signd | ||
ntvfs | ||
param | ||
rpc_server | ||
script | ||
scripting | ||
selftest | ||
setup | ||
smb_server | ||
smbd | ||
torture | ||
utils | ||
winbind | ||
wrepl_server | ||
.clang_complete | ||
.valgrind_suppressions | ||
wscript_build |