blob: 3a33b8b142008e87cc223e6ef1fe259a4fa3357e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
<samba:parameter name="smb2 disable lock sequence checking"
context="G"
type="boolean"
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
<para>This boolean parameter controls whether
<citerefentry><refentrytitle>smbd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> will disable
lock sequence checking even for multi-channel connections
as well as durable handles.
</para>
<para>The [MS-SMB2] specification (under 3.3.5.14 Receiving an SMB2 LOCK Request)
documents that a server should do lock sequence 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.
</para>
<para>But Windows Server (at least up to v2004) only does these checks
for the Open.IsResilient and Open.IsPersistent.
That means they do not implement the behavior specified
in [MS-SMB2].</para>
<para>By default Samba behaves according to the specification
and implements lock sequence checking when multi-channel is used.</para>
<para>Warning: Only enable this option if existing clients can't
handle lock sequence checking for handles without Open.IsResilient and Open.IsPersistent.
And it turns out that the Windows Server behavior is required.</para>
<para>Note: it's likely that this option will be removed again
if future Windows versions change their behavior.</para>
<para>Note: Samba does not implement Open.IsResilient and Open.IsPersistent yet.</para>
</description>
<related>server multi channel support</related>
<value type="default">no</value>
<value type="example">yes</value>
</samba:parameter>
|
