4 This is the second release candidate of Samba 4.8. 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.8 will be the next version of the Samba suite.
22 Adds Group Policy support for the Samba kdc. Applies password policies
23 (minimum/maximum password age, minimum password length, and password
24 complexity) and kerberos policies (user/service ticket lifetime and
27 Adds the samba_gpoupdate script for applying and unapplying
28 policy. Can be applied automatically by setting
30 'apply group policies = yes'.
32 Time Machine Support with vfs_fruit
33 -----------------------------------
35 Samba can be configured as a Time Machine target for Apple Mac devices
36 through the vfs_fruit module. When enabling a share for Time Machine
37 support the relevant Avahi records to support discovery will be published
38 for installations that have been built against the Avahi client library.
40 Shares can be designated as a Time Machine share with the following setting:
42 'fruit:time machine = yes'
44 Support for lower casing the MDNS Name
45 --------------------------------------
47 Allows the server name that is advertised through MDNS to be set to the
48 hostname rather than the Samba NETBIOS name. This allows an administrator
49 to make Samba registered MDNS records match the case of the hostname
50 rather than being in all capitals.
52 This can be set with the following settings:
59 Attributes deemed to be sensitive are now encrypted on disk. The sensitive
62 msDS-ExecuteScriptPassword
70 supplementalCredentials
76 This encryption is enabled by default on a new provision or join, it
77 can be disabled at provision or join time with the new option
78 '--plaintext-secrets'.
80 However, an in-place upgrade will not encrypt the database.
82 Once encrypted, it is not possible to do an in-place downgrade (eg to
83 4.7) of the database. To obtain an unencrypted copy of the database a
84 new DC join should be performed, specifying the '--plaintext-secrets'
87 The key file "encrypted_secrets.key" is created in the same directory
88 as the database and should NEVER be disclosed. It is included by the
91 Active Directory replication visualisation
92 ------------------------------------------
94 To work out what is happening in a replication graph, it is sometimes
95 helpful to use visualisations. We introduce a samba-tool subcommand to
96 write Graphviz dot output and generate text-based heatmaps of the
97 distance in hops between DCs.
99 There are two subcommands, two graphical modes, and (roughly) two modes of
100 operation with respect to the location of authority.
102 `samba-tool visualize ntdsconn` looks at NTDS Connections.
103 `samba-tool visualize reps` looks at repsTo and repsFrom objects.
105 In '--distance' mode (default), the distances between DCs are shown in
106 a matrix in the terminal. With '--color=yes', this is depicted as a
107 heatmap. With '--utf8' it is a lttle prettier.
109 In '--dot' mode, Graphviz dot output is generated. When viewed using
110 dot or xdot, this shows the network as a graph with DCs as vertices
111 and connections edges. Certain types of degenerate edges are shown in
112 different colours or line-styles.
114 NT4-style replication based net commands removed
115 ------------------------------------------------
117 The following commands and sub-commands have been removed from the
123 Also, replicating from a real NT4 domain with "net rpc vampire" and
124 "net rpc vampire keytab" has been removed.
126 The NT4-based commands were accidentially broken in 2013, and nobody
127 noticed the breakage. So instead of fixing them including tests (which
128 would have meant writing a server for the protocols, which we don't
129 have) we decided to remove them.
131 For the same reason, the "samsync", "samdeltas" and "database_redo"
132 commands have been removed from rpcclient.
134 "net rpc vampire keytab" from Active Directory domains continues to be
137 vfs_aio_linux module removed
138 ----------------------------
140 The current Linux kernel aio does not match what Samba would
141 do. Shipping code that uses it leads people to false
142 assumptions. Samba implements async I/O based on threads by default,
143 there is no special module required to see benefits of read and write
144 request being sent do the disk in parallel.
146 smbclient reparse point symlink parameters reversed
147 ---------------------------------------------------
149 A bug in smbclient caused the 'symlink' command to reverse the
150 meaning of the new name and link target parameters when creating a
151 reparse point symlink against a Windows server. As this is a
152 little used feature the ordering of these parameters has been
153 reversed to match the parameter ordering of the UNIX extensions
154 'symlink' command. The usage message for this command has also
155 been improved to remove confusion.
160 The dependency to global list of trusted domains within
161 the winbindd processes has been reduced a lot.
163 The construction of that global list is not reliable and often
164 incomplete in complex trust setups. In most situations the list is not needed
165 any more for winbindd to operate correctly. E.g. for plain file serving via SMB
166 using a simple idmap setup with autorid, tdb or ad. However some more complex
167 setups require the list, e.g. if you specify idmap backends for specific
168 domains. Some pam_winbind setups may also require the global list.
170 If you have a setup that doesn't require the global list, you should set
171 "winbind scan trusted domains = no".
173 VirusFilter VFS module
174 ----------------------
176 This new module integrates with Sophos, F-Secure and ClamAV anti-virus
177 software to provide scanning and filtering of files on a Samba share.
183 The two commands 'net serverid list' and 'net serverid wipe' have been
184 removed, because the file serverid.tdb is not used anymore.
186 'net serverid list' can be replaced by listing all files in the
187 subdirectory "msg.lock" of Samba's "lock directory". The unique id
188 listed by 'net serverid list' is stored in every process' lockfile in
191 'net serverid wipe' is not necessary anymore. It was meant primarily
192 for clustered environments, where the serverid.tdb file was not
193 properly cleaned up after single node crashes. Nowadays smbd and
194 winbind take care of cleaning up the msg.lock and msg.sock directories
201 Parameter Name Description Default
202 -------------- ----------- -------
203 apply group policies New no
206 client schannel Default changed/ yes
208 gpo update command New
209 ldap ssl ads Deprecated
210 map untrusted to domain Removed
211 oplock contention limit Removed
212 prefork children New 1
213 mdns name New netbios
214 fruit:time machine New false
217 server schannel Default changed/ yes
220 winbind scan trusted domains New yes
221 winbind trusted domains only Removed
224 CHANGES SINCE 4.8.0rc1
225 ======================
227 o Günther Deschner <gd@samba.org>
228 * BUG 13227: packaging: Fix default systemd-dir path.
229 * BUG 13238: build: Deal with recent glibc sunrpc header removal.
231 o Stefan Metzmacher <metze@samba.org>
232 * BUG 13228: repl_meta_data: fix linked attribute corruption on databases
233 with unsorted links on expunge.
235 o Christof Schmitt <cs@samba.org>
236 * BUG 13217: s3/smbd: Remove file system sharemode before calling unlink.
238 o Andreas Schneider <asn@samba.org>
239 * BUG 13209: Small improvements in winbindd for the resource cleanup in error
241 * BUG 13238: Make Samba work with tirpc and libnsl2.
247 https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.8#Release_blocking_bugs
250 #######################################
251 Reporting bugs & Development Discussion
252 #######################################
254 Please discuss this release on the samba-technical mailing list or by
255 joining the #samba-technical IRC channel on irc.freenode.net.
257 If you do report problems then please try to send high quality
258 feedback. If you don't provide vital information to help us track down
259 the problem then you will probably be ignored. All bug reports should
260 be filed under the Samba 4.1 and newer product in the project's Bugzilla
261 database (https://bugzilla.samba.org/).
264 ======================================================================
265 == Our Code, Our Bugs, Our Responsibility.
267 ======================================================================