selftest: Designate one testenv as having SMBv1 disabled
authorTim Beale <timbeale@catalyst.net.nz>
Thu, 22 Nov 2018 00:22:19 +0000 (13:22 +1300)
committerTim Beale <timbeale@samba.org>
Tue, 27 Nov 2018 02:43:17 +0000 (03:43 +0100)
commit160031f7b7e4e14a1b9ff9316b166fd52b7d401d
tree03a26bd236229ca97faf717a42297339c14b30f2
parent88ccd418fdee67ef8f2e4c06acc1488a875c641e
selftest: Designate one testenv as having SMBv1 disabled

We recommend users disable SMBv1 to avoid potential security holes.
However, none of the AD DC testenvs have SMBv1 disabled.

This patch disables SMBv1 on an arbitrarily-chosen testenv (restoredc).

I chose restoredc as we'll want to run the backup tool tests against
this target, and it might be useful to check we can backup a DC if it's
already been restored once.

Note that SMBv2 doesn't support POSIX extensions (only SMBv1 does),
which is why we haven't just disabled SMBv1 on *all* testenvs.

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

Signed-off-by: Tim Beale <timbeale@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
selftest/target/README
selftest/target/Samba4.pm