1 =================================
2 Release Notes for Samba 3.6.0pre1
4 =================================
7 This is the first preview release of Samba 3.6. This is *not*
8 intended for production environments and is designed for testing
9 purposes only. Please report any defects via the Samba bug reporting
10 system at https://bugzilla.samba.org/.
13 Major enhancements in Samba 3.6.0 include:
16 Changed security defaults
17 -------------------------
19 Samba 3.6 has adopted a number of improved security defaults that will
20 impact on existing users of Samba.
22 client ntlmv2 auth = yes
23 client use spnego principal = no
24 send spnego principal = no
26 The impact of 'client ntlmv2 auth = yes' is that by default we will not
27 use NTLM authentication as a client. This applies to the Samba client
28 tools such as smbclient and winbind, but does not change the separately
29 released in-kernel CIFS client. To re-enable the poorer NTLM encryption
30 set '--option=clientusentlmv2auth=no' on your smbclient command line, or
31 set 'client ntlmv2 auth = no' in your smb.conf
33 The impact of 'client use spnego principal = no' is that we may be able
34 to use Kerberos to communicate with a server less often in smbclient,
35 winbind and other Samba client tools. We may fall back to NTLMSSP in
36 more situations where we would previously rely on the insecure
37 indication from the 'NegProt' CIFS packet. This mostly occursed when
38 connecting to a name alias not recorded as a servicePrincipalName for
39 the server. This indication is not available from Windows 2008 or later
40 in any case, and is not used by modern Windows clients, so this makes
41 Samba's behaviour consistent with other clients and against all servers.
43 The impact of 'send spnego principal = no' is to match Windows 2008 and
44 not to send this principal, making existing clients give more consistent
45 behaviour (more likely to fall back to NTLMSSP) between Samba and
46 Windows 2008, and between Windows versions that did and no longer use
53 SMB2 support in 3.6.0 is fully functional (with one omission),
54 and can be enabled by setting:
58 in the [global] section of your smb.conf and re-starting
59 Samba. All features should work over SMB2 except the modification
60 of user quotas using the Windows quota management tools.
62 As this is the first release containing what we consider
63 to be a fully featured SMB2 protocol, we are not enabling
64 this by default, but encourage users to enable SMB2 and
65 test it. Once we have enough confirmation from Samba
66 users and OEMs that SMB2 support is stable in wide user
67 testing we will enable SMB2 by default in a future Samba
71 Internal Winbind passdb changes
72 -------------------------------
74 Winbind has been changed to use the internal samr and lsa rpc pipe to get
75 local user and group information instead of calling passdb functions. The
76 reason is to use more of our infrastructure and test this infrastructure by
77 using it. With this approach more code in Winbind is shared.
83 The spoolss and the old RAP printing code have been completely
84 overhauled and refactored.
86 All calls from lanman/printing code has been changed to go through the
87 spoolss RPC interfaces, this allows us to keep all checks in one place
88 and avoid special cases in the main printing code.
89 Printing code has been therefore confined within the spoolss code.
91 All the printing code, including the spoolss RPC interfaces has been
92 changed to use the winreg RPC interfaces to store all data.
93 All data has been migrated from custom, arbitrary TDB files to the
94 registry interface. This transition allow us to present correct data to
95 windows client accessing the server registry through the winreg RPC
96 interfaces to query for printer data. Data is served out from a real
97 registry implementation and therefore arguably 100% forward compatible.
99 Migration code from the previous TDB files formats is provided. This
100 code is automatically invoked the first time the new code is run on the
101 server. Although manual migration is also available using the 'net
102 printer migrate' command.
104 These changes not only make all the spoolss code much more closer to
105 "the spec", it also greatly improves our internal testing of both
106 spoolss and winreg interfaces, and reduces overall code duplication.
108 As part of this work, new tests have been also added to increase
111 This code will also allow, in future, an easy transition to split out
112 the spooling functions into a separate daemon for those OEMs that do not
113 need printing functionality in their appliances, reducing the code
120 Added the new SMB Traffic Analyzer (SMBTA) VFS module protocol 2
121 featuring encryption, multiple arguments, and easier parseability. A new
122 tool 'smbta-util' has been created to control the encryption behaviour
123 of SMBTA. For compatibility, SMBTA by default operates on version 1.
124 There are programs consuming the data that the module sends.
126 More information can be found on
127 http://holger123.wordpress.com/smb-traffic-analyzer/
130 NFS quota backend on Linux
131 --------------------------
133 A new nfs quota backend for Linux has been added that is based
134 on the existing Solaris/FreeBSD implementation. This allows samba
135 to communicate correct diskfree information for nfs imports that
136 are re-exported as samba shares.
139 ######################################################################
146 Parameter Name Description Default
147 -------------- ----------- -------
149 async smb echo handler New No
150 client ntlmv2 auth Changed Default Yes
151 client use spnego principal New No
152 ctdb locktime warn threshold New 0
153 idmap alloc backend Removed
154 log writeable files on exit New No
155 multicast dns register New Yes
157 send spnego principal New No
158 smb2 max credits New 128
159 smb2 max read New 1048576
160 smb2 max trans New 1048576
161 smb2 max write New 1048576
162 strict allocate Changed Default Yes
163 username map cache time New 0
164 winbind max clients New 200
167 ######################################################################
168 Reporting bugs & Development Discussion
169 #######################################
171 Please discuss this release on the samba-technical mailing list or by
172 joining the #samba-technical IRC channel on irc.freenode.net.
174 If you do report problems then please try to send high quality
175 feedback. If you don't provide vital information to help us track down
176 the problem then you will probably be ignored. All bug reports should
177 be filed under the Samba 3.6 product in the project's Bugzilla
178 database (https://bugzilla.samba.org/).
181 ======================================================================
182 == Our Code, Our Bugs, Our Responsibility.
184 ======================================================================