4 This is the first 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.
23 The logging code now supports logging to multiple backends. In
24 addition to the previously available syslog and file backends, the
25 backends for logging to the systemd-journal, lttng and gpfs have been
26 added. Please consult the section for the 'logging' parameter in the
27 smb.conf manpage for details.
32 Support for Apple's Spotlight has been added by integrating with Gnome
35 For detailed instructions how to build and setup Samba for Spotlight,
36 please see the Samba wiki: <https://wiki.samba.org/index.php/Spotlight>
38 New FileChangeNotify subsystem
39 ------------------------------
41 Samba now contains a new subsystem to do FileChangeNotify. The
42 previous system used a central database, notify_index.tdb, to store
43 all notification requests. In particular in a cluster this turned out
44 to be a major bottleneck, because some hot records need to be bounced
45 back and forth between nodes on every change event like a new created
48 The new FileChangeNotify subsystem works with a central daemon per
49 node. Every FileChangeNotify request and every event are handled by an
50 asynchronous message from smbd to the notify daemon. The notify daemon
51 maintains a database of all FileChangeNotify requests in memory and
52 will distribute the notify events accordingly. This database is
53 asynchronously distributed in the cluster by the notify daemons.
55 The notify daemon is supposed to scale a lot better than the previous
56 implementation. The functional advantage is cross-node kernel change
57 notify: Files created via NFS will be seen by SMB clients on other
58 nodes per FileChangeNotify, despite the fact that popular cluster file
59 systems do not offer cross-node inotify.
61 Two changes to the configuration were required for this new subsystem:
62 The parameters "change notify" and "kernel change notify" are not
63 per-share anymore but must be set globally. So it is no longer
64 possible to enable or disable notify per share, the notify daemon has
65 no notion of a share, it only works on absolute paths.
67 New SMB profiling code
68 ----------------------
70 The code for SMB (SMB1, SMB2 and SMB3) profiling uses a tdb instead
71 of sysv IPC shared memory. This avoids performance problems and NUMA
72 effects. The profile stats are a bit more detailed than before.
74 Improved DCERPC man in the middle detection for kerberos
75 --------------------------------------------------------
77 The gssapi based kerberos backends for gensec have support for
78 DCERPC header signing when using DCERPC_AUTH_LEVEL_PRIVACY.
80 SMB signing required in winbindd by default
81 -------------------------------------------
83 The effective value for "client signing" is required
84 by default for winbindd, if the primary domain uses active directory.
86 Experimental NTDB was removed
87 -----------------------------
89 The experimental NTDB library introduced in Samba 4.0 has been
92 Improved support for trusted domains (as AD DC)
93 -----------------------------------------------
95 The support for trusted domains/forests has improved a lot.
97 samba-tool got "domain trust" subcommands to manage trusts:
99 create - Create a domain or forest trust.
100 delete - Delete a domain trust.
101 list - List domain trusts.
102 namespaces - Manage forest trust namespaces.
103 show - Show trusted domain details.
104 validate - Validate a domain trust.
106 External trusts between individual domains work in both ways
107 (inbound and outbound). The same applies to root domains of
108 a forest trust. The transitive routing into the other forest
109 is fully functional for kerberos, but not yet supported for NTLMSSP.
111 While a lot of things are working fine, there are currently a few limitations:
113 - Both sides of the trust need to fully trust each other!
114 - No SID filtering rules are applied at all!
115 - This means DCs of domain A can grant domain admin rights
117 - It's not possible to add users/groups of a trusted domain
123 Both client and server have support for SMB 3.1.1 now.
125 This is the dialect introduced with Windows 10, it improves the secure
126 negotiation of SMB dialects and features.
128 New smbclient subcommands
129 -------------------------
131 - Query a directory for change notifications: notify <dir name>
132 - Server side copy: scopy <source filename> <destination filename>
134 New rpcclient subcommands
135 -------------------------
137 netshareenumall - Enumerate all shares
138 netsharegetinfo - Get Share Info
139 netsharesetinfo - Set Share Info
140 netsharesetdfsflags - Set DFS flags
141 netfileenum - Enumerate open files
142 netnamevalidate - Validate sharename
143 netfilegetsec - Get File security
144 netsessdel - Delete Session
145 netsessenum - Enumerate Sessions
146 netdiskenum - Enumerate Disks
147 netconnenum - Enumerate Connections
148 netshareadd - Add share
149 netsharedel - Delete share
154 idmap_script - see 'man 8 idmap_script'
155 vfs_unityed_media - see 'man 8 vfs_unityed_media'
156 vfs_shell_snap - see 'man 8 vfs_shell_snap'
158 ######################################################################
165 Parameter Name Description Default
166 -------------- ----------- -------
168 msdfs shuffle referrals New no
169 smbd profiling level New off
171 tls priority New NORMAL:-VERS-SSL3.0
173 change notify Changed to [global]
174 kernel change notify Changed to [global]
175 client max protocol Changed default SMB3_11
176 server max protocol Changed default SMB3_11
181 vfs_notify_fam - see section 'New FileChangeNotify subsystem'.
188 #######################################
189 Reporting bugs & Development Discussion
190 #######################################
192 Please discuss this release on the samba-technical mailing list or by
193 joining the #samba-technical IRC channel on irc.freenode.net.
195 If you do report problems then please try to send high quality
196 feedback. If you don't provide vital information to help us track down
197 the problem then you will probably be ignored. All bug reports should
198 be filed under the Samba 4.3 product in the project's Bugzilla
199 database (https://bugzilla.samba.org/).
202 ======================================================================
203 == Our Code, Our Bugs, Our Responsibility.
205 ======================================================================