Jones Syue 薛懷宗
2024-Apr-01 10:03 UTC
[Samba] Bad SMB2 (sign_algo_id=1) signature for message
> [2024/03/01 15:59:00.612141, 0, pid=1778617] libcli/smb/smb2_signing.c:639(smb2_signing_check_pdu) > Bad SMB2 (sign_algo_id=1) signature for messageHello Michael, what is the linux distro and samba version in your env, thank you :) It looks like a client-side tool could see similar output, from my env: $ rpcclient -U 'nobody%nobody' -c 'netshareenumall' 127.0.0.1 Bad SMB2 (sign_algo_id=2) signature for message [0000] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ [0000] 3B F0 CD 43 12 2D 1F D2 47 30 64 EE 8C 45 29 D2 ;..C.-.. G0d..E). Cannot connect to server. Error was NT_STATUS_ACCESS_DENIED $ rpcclient --version Version 4.15.13-Ubuntu My environment is: Ubuntu 22.04.4 LTS Samba 4.15.13 -- Regards, Jones Syue | ??? QNAP Systems, Inc.
Michael Tokarev
2024-Apr-01 10:09 UTC
[Samba] Bad SMB2 (sign_algo_id=1) signature for message
01.04.2024 13:03, Jones Syue ???:>> [2024/03/01 15:59:00.612141, 0, pid=1778617] libcli/smb/smb2_signing.c:639(smb2_signing_check_pdu) >> Bad SMB2 (sign_algo_id=1) signature for message > > Hello Michael, > > what is the linux distro and samba version in your env, thank you :)It does not depend on linux distro for sure. Everything is within samba. So far it happened with samba version 4.17, 4.18 and 4.19 (various patch levels). I can't say for sure but I *think* each time the client is windows server 2012. I don't think this will help you in any way though :)> It looks like a client-side tool could see similar output, from my env: > $ rpcclient -U 'nobody%nobody' -c 'netshareenumall' 127.0.0.1 > Bad SMB2 (sign_algo_id=2) signature for message > [0000] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ > [0000] 3B F0 CD 43 12 2D 1F D2 47 30 64 EE 8C 45 29 D2 ;..C.-.. G0d..E). > Cannot connect to server. Error was NT_STATUS_ACCESS_DENIEDExactly the same happens when I run that command here (with sama 4.19.5). /mjt