Bug 14858 - smb2_signing_check_pdu: smb2_signing_calc_signature(sign_algo_id=1) - NT_STATUS_INTERNAL_ERROR
Summary: smb2_signing_check_pdu: smb2_signing_calc_signature(sign_algo_id=1) - NT_STAT...
Status: RESOLVED DUPLICATE of bug 14855
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.15.0
Hardware: All All
: P5 minor (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-07 21:36 UTC by Peter Eriksson
Modified: 2021-10-21 15:55 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Eriksson 2021-10-07 21:36:08 UTC 
Started noticing these in the Samba logs now on a couple of our servers:

[2021/10/07 23:26:02.557294,  0] ../../libcli/smb/smb2_signing.c:433(smb2_signing_calc_signature)
  smb2_signing_calc_signature: opcode[12] msg_id == 0

[2021/10/07 23:26:02.557342,  0] ../../libcli/smb/smb2_signing.c:705(smb2_signing_check_pdu)
  smb2_signing_check_pdu: smb2_signing_calc_signature(sign_algo_id=1) - NT_STATUS_INTERNAL_ERROR

Most users seems to be able to login just fine so I'm assuming this is some specific client doing something strange?
Comment 1 Jeremy Allison 2021-10-21 15:55:49 UTC 

*** This bug has been marked as a duplicate of bug 14855 ***