4 This is the second release candidate of Samba 4.3. 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.3 will be the next version of the Samba suite.
24 The logging code now supports logging to multiple backends. In
25 addition to the previously available syslog and file backends, the
26 backends for logging to the systemd-journal, lttng and gpfs have been
27 added. Please consult the section for the 'logging' parameter in the
28 smb.conf manpage for details.
33 Support for Apple's Spotlight has been added by integrating with Gnome
36 For detailed instructions how to build and setup Samba for Spotlight,
37 please see the Samba wiki: <https://wiki.samba.org/index.php/Spotlight>
39 New FileChangeNotify subsystem
40 ------------------------------
42 Samba now contains a new subsystem to do FileChangeNotify. The
43 previous system used a central database, notify_index.tdb, to store
44 all notification requests. In particular in a cluster this turned out
45 to be a major bottleneck, because some hot records need to be bounced
46 back and forth between nodes on every change event like a new created
49 The new FileChangeNotify subsystem works with a central daemon per
50 node. Every FileChangeNotify request and every event are handled by an
51 asynchronous message from smbd to the notify daemon. The notify daemon
52 maintains a database of all FileChangeNotify requests in memory and
53 will distribute the notify events accordingly. This database is
54 asynchronously distributed in the cluster by the notify daemons.
56 The notify daemon is supposed to scale a lot better than the previous
57 implementation. The functional advantage is cross-node kernel change
58 notify: Files created via NFS will be seen by SMB clients on other
59 nodes per FileChangeNotify, despite the fact that popular cluster file
60 systems do not offer cross-node inotify.
62 Two changes to the configuration were required for this new subsystem:
63 The parameters "change notify" and "kernel change notify" are not
64 per-share anymore but must be set globally. So it is no longer
65 possible to enable or disable notify per share, the notify daemon has
66 no notion of a share, it only works on absolute paths.
68 New SMB profiling code
69 ----------------------
71 The code for SMB (SMB1, SMB2 and SMB3) profiling uses a tdb instead
72 of sysv IPC shared memory. This avoids performance problems and NUMA
73 effects. The profile stats are a bit more detailed than before.
75 Improved DCERPC man in the middle detection for kerberos
76 --------------------------------------------------------
78 The gssapi based kerberos backends for gensec have support for
79 DCERPC header signing when using DCERPC_AUTH_LEVEL_PRIVACY.
81 SMB signing required in winbindd by default
82 -------------------------------------------
84 The effective value for "client signing" is required
85 by default for winbindd, if the primary domain uses active directory.
87 Experimental NTDB was removed
88 -----------------------------
90 The experimental NTDB library introduced in Samba 4.0 has been
93 Improved support for trusted domains (as AD DC)
94 -----------------------------------------------
96 The support for trusted domains/forests has improved a lot.
98 samba-tool got "domain trust" subcommands to manage trusts:
100 create - Create a domain or forest trust.
101 delete - Delete a domain trust.
102 list - List domain trusts.
103 namespaces - Manage forest trust namespaces.
104 show - Show trusted domain details.
105 validate - Validate a domain trust.
107 External trusts between individual domains work in both ways
108 (inbound and outbound). The same applies to root domains of
109 a forest trust. The transitive routing into the other forest
110 is fully functional for kerberos, but not yet supported for NTLMSSP.
112 While a lot of things are working fine, there are currently a few limitations:
114 - Both sides of the trust need to fully trust each other!
115 - No SID filtering rules are applied at all!
116 - This means DCs of domain A can grant domain admin rights
118 - It's not possible to add users/groups of a trusted domain
124 Both client and server have support for SMB 3.1.1 now.
126 This is the dialect introduced with Windows 10, it improves the secure
127 negotiation of SMB dialects and features.
129 New smbclient subcommands
130 -------------------------
132 - Query a directory for change notifications: notify <dir name>
133 - Server side copy: scopy <source filename> <destination filename>
135 New rpcclient subcommands
136 -------------------------
138 netshareenumall - Enumerate all shares
139 netsharegetinfo - Get Share Info
140 netsharesetinfo - Set Share Info
141 netsharesetdfsflags - Set DFS flags
142 netfileenum - Enumerate open files
143 netnamevalidate - Validate sharename
144 netfilegetsec - Get File security
145 netsessdel - Delete Session
146 netsessenum - Enumerate Sessions
147 netdiskenum - Enumerate Disks
148 netconnenum - Enumerate Connections
149 netshareadd - Add share
150 netsharedel - Delete share
155 idmap_script - see 'man 8 idmap_script'
156 vfs_unityed_media - see 'man 8 vfs_unityed_media'
157 vfs_shell_snap - see 'man 8 vfs_shell_snap'
159 New sparsely connected replia graph (Improved KCC)
160 --------------------------------------------------
162 The Knowledge Consistency Checker (KCC) maintains a replication graph
163 for DCs across an AD network. The existing Samba KCC uses a fully
164 connected graph, so that each DC replicates from all the others, which
165 does not scale well with large networks. In 4.3 there is an
166 experimental new KCC that creates a sparsely connected replication
167 graph and closely follows Microsoft's specification. It is turned off
168 by default. To use the new KCC, set "kccsrv:samba_kcc=true" in
169 smb.conf and let us know how it goes. You should consider doing this
170 if you are making a large new network. For small networks there is
171 little benefit and you can always switch over at a later date.
173 Configurable TLS protocol support, with better defaults
174 -------------------------------------------------------
176 The "tls priority" option can be used to change the supported TLS
177 protocols. The default is to disable SSLv3, which is no longer
181 ######################################################################
188 Parameter Name Description Default
189 -------------- ----------- -------
191 msdfs shuffle referrals New no
192 smbd profiling level New off
194 tls priority New NORMAL:-VERS-SSL3.0
196 change notify Changed to [global]
197 kernel change notify Changed to [global]
198 client max protocol Changed default SMB3_11
199 server max protocol Changed default SMB3_11
204 vfs_notify_fam - see section 'New FileChangeNotify subsystem'.
213 CHANGES SINCE 4.2.0rc1
214 ======================
216 o Jeremy Allison <jra@samba.org>
217 * BUG 11359: strsep is not available on Solaris
219 o Björn Baumbach <bb@sernet.de>
220 * BUG 11421: Build with GPFS support is broken
222 o Justin Maggard <jmaggard@netgear.com>
223 * BUG 11320: "force group" with local group not working
225 o Martin Schwenke <martin@meltin.net
226 * BUG 11424: Build broken with --disable-python
229 #######################################
230 Reporting bugs & Development Discussion
231 #######################################
233 Please discuss this release on the samba-technical mailing list or by
234 joining the #samba-technical IRC channel on irc.freenode.net.
236 If you do report problems then please try to send high quality
237 feedback. If you don't provide vital information to help us track down
238 the problem then you will probably be ignored. All bug reports should
239 be filed under the "Samba 4.1 and newer" product in the project's Bugzilla
240 database (https://bugzilla.samba.org/).
243 ======================================================================
244 == Our Code, Our Bugs, Our Responsibility.
246 ======================================================================