Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

SMB3 signatures

I have only Windows Server 2016 and 10 machines on my network. I have enabled SMB3 encryption on all the servers that have file shares on them and I have configures SMB Digitally Signing to Required for all the machines in the domain. I would like to find out if my SMB connections are digitally signed. I used Wireshark to capture a connection between my Windows 10 1709 machine and Windows Server 2016 file share.

I cant attach a screenshot but in the "Negotiate Protocol Response" packet it shows the "Signature" under SMB2 Header as 00000000000000000000000000000000 so I assume SMB digitally signing isn't working?

The weird thing is, if I open an "Encrypted SMB3" packet and expand the SMB2 Transform Header I can see a Signature option which says: ee51ab3d9aa14b72cb8df4302b582167

So is SMB3 digitally signing working or not?

SMB3 signatures

I have only Windows Server 2016 and 10 machines on my network. I have enabled SMB3 encryption on all the servers that have file shares on them and I have configures SMB Digitally Signing to Required for all the machines in the domain. I would like to find out if my SMB connections are digitally signed. I used Wireshark to capture a connection between my Windows 10 1709 machine and Windows Server 2016 file share.

I cant attach a screenshot but in the "Negotiate Protocol Response" packet it shows the "Signature" under SMB2 Header as 00000000000000000000000000000000 so I assume SMB digitally signing isn't working?

The weird thing is, if I open an "Encrypted SMB3" packet and expand the SMB2 Transform Header I can see a Signature option which says: ee51ab3d9aa14b72cb8df4302b582167

So is SMB3 digitally signing working or not?