SMB signing requirements
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 82fc013 · +2 −2 lines · also on GitHub
⋯ 48 unchanged lines
4949
Data Type: `REG_DWORD`
5050
Data: 0 (disable), 1 (enable)
5151
s
52
−**Note** In these policies *always* indicates that SMB signing is required, and *if server agrees* or *if client agrees* indicates that SMB signing is enabled.
52
+**Note** In these policies *always* indicates that SMB signing is required.
5353
5454
### Understanding "RequireSecuritySignature" and "EnableSecuritySignature"
5555
56
−The **EnableSecuritySignature** registry setting for SMB2 and later clients and servers is ignored. Therefore, this setting does nothing unless you're using SMB1. SMB 2.02 and later signing is controlled solely by being required or not. This setting is used when either the server or client requires SMB signing. Signing doesn't occur Only when both the server and client have signing set to **0**.
56
+The **EnableSecuritySignature** registry setting for SMB2 and later clients and servers is ignored. Therefore, this setting does nothing unless you're using SMB1. SMB 2.02 and later signing is controlled solely by being required or not. This setting is used when either the server or client requires SMB signing. Signing doesn't occur only when both the server and client have signing set to **0**.
5757
5858
In summary SMB is signed when:
5959
⋯ 19 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 09:45 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.