Add know fail for these tests that run against ad_member
which won't succeed because SMB1 isn't supported
However we do have some coverage with s4member (which depends on
ad_dc_ntvfs) which still supports SMB1.
Additionally remove the associated entries from skip_smb1_fail
Signed-off-by: Noel Power <noel.power@suse.com>
Reviewed-by: Ralph Boehme <slow@samba.org>
^samba3.unix.whoami kerberos connection.whoami\(ad_member\)
^samba3.unix.whoami anonymous connection.whoami\(ad_member\)
^samba3.unix.whoami ntlm user@realm.whoami\(ad_member\)
+^samba4.smb.signing disabled on with -k no --signing=off domain-creds.xcopy\(ad_member\)
+^samba4.smb.signing disabled on with -k no --option=gensec:spengo=no --signing=off domain-creds.xcopy\(ad_member\)
+^samba4.smb.signing disabled on with -k yes --signing=off domain-creds.xcopy\(ad_member\)
^samba3.blackbox.smbclient_basic.NT1\(nt4_dc_schannel\)
^samba4.blackbox.smbclient\(ad_member:local\)\(ad_member:local\)
^samba4.blackbox.smbclient\(chgdcpass:local\)\(chgdcpass:local\)
-^samba4.smb.signing disabled on with -k no --option=gensec:spengo=no --signing=off domain-creds\(ad_member\)
-^samba4.smb.signing disabled on with -k no --signing=off domain-creds\(ad_member\)
-^samba4.smb.signing disabled on with -k yes --signing=off domain-creds\(ad_member\)