s4:torture/smb2: add smb2.session.bind_negative_{smb202,smb210,smb2to3,smb3to2,smb3to3}
commit457b989881634bfe073cf47a4184f95823a558be
authorStefan Metzmacher <metze@samba.org>
Wed, 24 Feb 2021 16:43:40 +0000 (24 17:43 +0100)
committerJeremy Allison <jra@samba.org>
Wed, 17 Mar 2021 00:49:32 +0000 (17 00:49 +0000)
treeb03a20f9156c0e761d3f7df53cec1718048c9843
parent30fa5a45c2df42cc5c28a912cb4f11f514a89390
s4:torture/smb2: add smb2.session.bind_negative_{smb202,smb210,smb2to3,smb3to2,smb3to3}

'smb2.session.bind_negative_smb202' is similar to the MultipleChannel_Negative_SMB2002 test
from the Windows Protocol Test Suite.

It demonstrates that the server needs to do lookup
in the global session table in order to get the signing
and error code of invalid session setups correct.

In order to work out the details I've added more similar tests.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=14512

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
selftest/knownfail.d/smb2.session [new file with mode: 0644]
source4/torture/smb2/session.c