Jeremy Allison f3281e0bef s3: selftest: Add new SMB1-only wildcard unlink regression test. ... samba3.smbtorture_s3.crypt_client.SMB1-WILD-MANGLE-UNLINK(nt4_dc_smb1) samba3.smbtorture_s3.plain.SMB1-WILD-MANGLE-UNLINK(fileserver_smb1) knownfail for now. The recent wildcard changes broke something that used to work. Consider a directory with 2 files: dir/ a * The '*' file has a mangled name of _2X68P~X. SMB1unlink("_2X68P~X") will delete *both* files as the new 'unlink has wildcard' check is done after the name unmangle. SMB2 doesn't suffer from this problem, as it doesn't allow wildcard unlinks. Fix to follow. Signed-off-by: Jeremy Allison <jra@samba.org> Reviewed-by: Ralph Boehme <slow@samba.org>		2020-10-08 15:07:30 +00:00
..
ktest-krb5_ccache-2	s3-selftest Add tests to show kerberos works across a password change	2011-04-06 05:24:48 +02:00
ktest-krb5_ccache-3	s3-selftest Add tests to show kerberos works across a password change	2011-04-06 05:24:48 +02:00
ktest-secrets.tdb	s3-selftest Add tests to show kerberos works across a password change	2011-04-06 05:24:48 +02:00
tests.py	s3: selftest: Add new SMB1-only wildcard unlink regression test.	2020-10-08 15:07:30 +00:00