| blob | 25bd1ab4f6eec4968a6e049c873818268841c8f9 |
1 Release Announcements
2 =====================
4 This is the second release candidate of Samba 4.0. This is *not*
5 intended for production environments and is designed for testing
6 purposes only. Please report any defects via the Samba bug reporting
7 system at https://bugzilla.samba.org/.
9 Samba 4.0 will be the next version of the Samba suite and incorporates
10 all the technology found in both the Samba4 series and the
11 stable 3.x series. The primary additional features over Samba 3.6 are
12 support for the Active Directory logon protocols used by Windows 2000
13 and above.
15 This release contains the best of all of Samba's
16 technology parts, both a file server (that you can reasonably expect
17 to upgrade existing Samba 3.x releases to) and the AD domain
18 controller work previously known as 'samba4'.
20 If you are upgrading, or looking to develop, test or deploy Samba 4.0
21 releases candidates, you should backup all configuration and data.
24 UPGRADING
25 =========
27 Users upgrading from Samba 3.x domain controllers and wanting to use
28 Samba 4.0 as an AD DC should use the 'samba-tool domain
29 classicupgrade' command. See the wiki for more details:
30 https://wiki.samba.org/index.php/Samba4/samba3upgrade/HOWTO.
32 Users upgrading from Samba 4.0 alpha and beta releases since alpha15
33 should run 'samba-tool dbcheck --cross-ncs --fix' before re-starting
34 Samba. Users upgrading from earlier alpha releases should contact the
35 team for advice.
37 Users upgrading an AD DC from any previous release should run
38 'samba-tool ntacl sysvolreset' to re-sync ACLs on the sysvol share
39 with those matching the GPOs in LDAP and the defaults from an initial
40 provision. This will set an underlying POSIX ACL if required (eg not
41 using the NTVFS file server).
43 If you used the BIND9_FLATFILE or BIND9_DLZ features,
44 you'll have to add '-dns' to the 'server services' option,
45 as the internal dns server (SAMBA_INTERNAL) is the default now.
48 NEW FEATURES
49 ============
51 Samba 4.0 supports the server-side of the Active Directory logon
52 environment used by Windows 2000 and later, so we can do full domain
53 join and domain logon operations with these clients.
55 Our Domain Controller (DC) implementation includes our own built-in
56 LDAP server and Kerberos Key Distribution Center (KDC) as well as the
57 Samba3-like logon services provided over CIFS. We correctly generate
58 the infamous Kerberos PAC, and include it with the Kerberos tickets we
59 issue.
61 Samba 4.0.0rc2 ships with two distinct file servers. We now use the
62 file server from the Samba 3.x series 'smbd' for all file serving by
63 default.
65 Samba 4.0 also ships with the 'NTVFS' file server. This file server
66 is what was used in all previous releases of Samba 4.0, and is
67 tuned to match the requirements of an AD domain controller. We
68 continue to support this, not only to provide continuity to
69 installations that have deployed it as part of an AD DC, but also as a
70 running example of the NT-FSA architecture we expect to move smbd to in
71 the longer term.
73 For pure file server work, the binaries users would expect from that
74 series (nmbd, winbindd, smbpasswd) continue to be available. When
75 running an AD DC, you only need to run 'samba' (not
76 nmbd/smbd/winbind), as the required services are co-coordinated by this
77 master binary.
79 As DNS is an integral part of Active Directory, we also provide two DNS
80 solutions, a simple internal DNS server for 'out of the box' configurations
81 and a more elaborate BIND plugin using the BIND DLZ mechanism in versions
82 9.8 and 9.9. During the provision, you can select which backend to use.
83 With the internal backend, your DNS server is good to go.
84 If you chose the BIND_DLZ backend, a configuration file will be generated
85 for bind to make it use this plugin, as well as a file explaining how to
86 set up bind.
88 To provide accurate timestamps to Windows clients, we integrate with
89 the NTP project to provide secured NTP replies. To use you need to
90 start ntpd and configure it with the 'restrict ... ms-sntp' and
91 ntpsigndsocket options.
93 Finally, a new scripting interface has been added to Samba 4, allowing
94 Python programs to interface to Samba's internals, and many tools and
95 internal workings of the DC code is now implemented in python.
98 ######################################################################
99 Changes
100 #######
102 smb.conf changes
103 ----------------
105 Parameter Name Description Default
106 -------------- ----------- -------
108 allow dns updates New secure only
109 announce as Removed
110 announce version Removed
111 cldap port New 0
112 client max protocol New
113 client min protocol New
114 client signing Changed default default
115 dcerpc endpoint servers New
116 dgram port New 0
117 directory security mask Removed
118 display charset Removed
119 dns forwarder New
120 dns update command New
121 force security mode Removed
122 force directory security mode Removed
123 homedir map Changed default auto.home
124 kernel share modes New Yes
125 kpasswd port New 0
126 krb5 port New 0
127 max protocol Removed
128 min protocol Removed
129 nbt client socket address New 0.0.0.0
130 nbt port New 0
131 nsupdate command New
132 ntp signd socket directory New
133 ntvfs handler New
134 paranoid server security Removed
135 pid directory New
136 printer admin Removed
137 rndc command New
138 rpc big endian New No
139 samba kcc command New
140 security mask Removed
141 send spnego principal Removed
142 server max protocol New SMB3
143 server min protocol New LANMAN1
144 server role New auto
145 server services New
146 server signing Changed default default
147 share backend New
148 share modes Removed
149 smb2 max read Changed default 1048576
150 smb2 max write Changed default 1048576
151 smb2 max trans Changed default 1048576
152 socket address Removed
153 spn update command New
154 time offset Removed
155 tls cafile New
156 tls certfile New
157 tls crlfile New
158 tls dh params file New
159 tls enabled New No
160 tls keyfile New
161 unicode New Yes
162 web port New 0
163 winbindd privileged socket directory New
164 winbind sealed pipes New No
165 winbindd socket directory New
168 CHANGES SINCE 4.0.0rc1
169 ======================
171 o Michael Adam <obnox@samba.org>
172 * BUG 9173: Make the SMB2 compound request create/delete_on_close/
173 close work as Windows.
176 o Jeremy Allison <jra@samba.org>
177 * BUG 9161: Re-add the vfs_Chdir() cache.
178 * BUG 9189: SMB2 Create doesn't return correct MAX ACCESS access mask in
179 blob.
180 * BUG 9213: Bad ASN.1 NegTokenInit packet can cause invalid free.
183 o Christian Ambach <ambi@samba.org>
184 * BUG 9162: Fix the build of the GPFS VFS module.
185 * BUG 9197: Only do 'printing_subsystem_update' when printing is enabled.
188 o Alexander Bokovoy <ab@samba.org>
189 * BUG 9157: Cleanup idmap_ldap build dependencies.
192 o Ira Cooper <ira@samba.org>
193 * BUG 9162: Fix build on Illumos/Solaris using '--with-acl'.
194 * BUG 9173: Compound requests should continue processing.
197 o Björn Jacke <bj@sernet.de>
198 * BUG 9162: Fix the build of the ACL VFS modules.
199 * BUG 9172: Fix reporting of gfs2 quotas.
202 o Volker Lendecke <vl@samba.org>
203 * BUG 9217: CreateFile with FILE_DIRECTORY_FILE can create directories
204 on read-only shares.
207 o Stefan Metzmacher <metze@samba.org>
208 * BUG 9173: Make the SMB2 compound request create/delete_on_close/
209 close work as Windows.
210 * BUG 9184: Fix receiving of UDP packets from 0 bytes.
211 * BUG 9191: Release the share mode lock before calling exit_server().
212 * BUG 9193: Fix usage of invalid memory in smb2_signing_check_pdu().
213 * BUG 9194: Disallow '--prefix=/usr' and '--prefix=/usr/local' without
214 '--enable-fhs'.
215 * BUG 9198: Fix RHEL-CTDB packaging.
218 o Matthieu Patou <mat@matws.net>
219 * BUG 9199: Fix usage of "panic action".
222 o Andreas Schneider <asn@samba.org>
223 * BUG 8632: Fix builtin forms order to match Windows again.
224 * BUG 9159: Fix generating idmap manpages.
225 * BUG 9218: Don't segfault if user specified ports out for range.
228 KNOWN ISSUES
229 ============
231 - 'samba-tool domain classicupgrade' will fail when setting ACLs on
232 the GPO folders with NT_STATUS_INVALID_ONWER in the default
233 configuration. This happens if, as is typical a 'domain admins'
234 group (-512) is mapped in the passdb backend being upgraded. This
235 is because the group mapping to a GID only prevents Samba from
236 allocating a uid for that group. The uid is needed so the 'domain
237 admins' group can own the GPO file objects.
239 To work around this issue, remove the 'domain admins' group before
240 upgrade, as it will be re-created automatically. You will
241 of course need to fill in the group membership again. A future release
242 will make this automatic, or find some other workaround.
244 - This release makes the s3fs file server the default, as this is the
245 file server combination we will use for the Samba 4.0 release.
247 - For similar reasons, sites with ACLs stored by the ntvfs file server
248 may wish to continue to use that file server implementation, as a
249 posix ACL will similarly not be set in this case.
251 - Replication of DNS data from one AD server to another may not work.
252 The DNS data used by the internal DNS server and bind9_dlz is stored
253 in an application partition in our directory. The replication of
254 this partition is not yet reliable.
256 - Replication may fail on FreeBSD due to getaddrinfo() rejecting names
257 containing _. A workaround will be in a future release.
259 - samba_upgradeprovision should not be run when upgrading to this release
260 from a recent release. No important database format changes have
261 been made since alpha16.
263 - Installation on systems without a system iconv (and developer
264 headers at compile time) is known to cause errors when dealing with
265 non-ASCII characters.
267 - Domain member support in the 'samba' binary is in its infancy, and
268 is not comparable to the support found in winbindd. As such, do not
269 use the 'samba' binary (provided for the AD server) on a member
270 server.
272 - There is no NetBIOS browsing support (network neighbourhood)
273 available for the AD domain controller. (Support in nmbd and smbd
274 for classic domains and member/standalone servers is unchanged).
276 - Clock Synchronisation is critical. Many 'wrong password' errors are
277 actually due to Kerberos objecting to a clock skew between client
278 and server. (The NTP work in the previous alphas are partly to assist
279 with this problem).
281 - The DRS replication code may fail. Please contact the team if you
282 experience issues with DRS replication, as we have fixed many issues
283 here in response to feedback from our production users.
286 RUNNING Samba 4.0 as an AD DC
287 =============================
289 A short guide to setting up Samba 4 as an AD DC can be found on the wiki:
291 http://wiki.samba.org/index.php/Samba4/HOWTO
293 #######################################
294 Reporting bugs & Development Discussion
295 #######################################
297 Please discuss this release on the samba-technical mailing list or by
298 joining the #samba-technical IRC channel on irc.freenode.net.
300 If you do report problems then please try to send high quality
301 feedback. If you don't provide vital information to help us track down
302 the problem then you will probably be ignored. All bug reports should
303 be filed under the Samba 4.0 product in the project's Bugzilla
304 database (https://bugzilla.samba.org/).
307 ======================================================================
308 == Our Code, Our Bugs, Our Responsibility.
309 == The Samba Team
310 ======================================================================