The Samba-Bugzilla – Bug 11209
samba-tool testparm output is unreliabe
Last modified: 2015-04-13 20:59:05 UTC
In Samba 4.1 the defaul of server max protocol is SMB3.
samba-tool testparm -v says that it is NT1 though.
I cross-checked that SMB3 is really the used default value. Setting it to NT1 explicitly works as expected and really sets is to NT1.
The output of "samba-tool testparm -v" is just incorect.
Another difference to the testparm tool is that "samba-tool testparm" gives back every explicitly set parameter from smb.conf, even when they are set to the default values.
This is already fixed in 4.2.
In 4.1 samba-tool testparm -v showed the default for the source4/smb_server...
I don't think we'll backport all the patches to 4.1...
Agreed. Even if we could backport them, it would change defaults and generally do things we just don't do in a point release.
On 2015-04-12 at 03:19 +0000 firstname.lastname@example.org sent off:
> --- Comment #3 from Andrew Bartlett <email@example.com> ---
> Agreed. Even if we could backport them, it would change defaults and generally
> do things we just don't do in a point release.
Andrew, you didn't get the actual point of the bug report. It would just ouput the
actually used defaults, not change defaults. If you would put the output of
"samba-tool testparm -v" into a smb.conf, then you would change the default
values (like you would set server max protocol to NT1 even though the actual
default is SMB3).
samba-tool testparm shows the actually used defaults for the source4 code. Yes, I realise it is hard to comprehend the horror, but we shipped Samba 4.0 with different defaults for code in different parts of the tree!
Andrew, please read the initial report and don't say it's wrong without *verifying* it :). If you don't believe it, then please run samba-tool testparm -v on a 4.1 AD server, see that server max protocol is said to be NT1. Then make a network sniff to see that the server actually speaks smb3.