4 This is the first preview release 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 'server services = +gpoupdate'.
32 Time Machine Support with vfs_fruit
33 ===================================
34 Samba can be configured as a Time Machine target for Apple Mac devices
35 through the vfs_fruit module. When enabling a share for Time Machine
36 support the relevant Avahi records to support discovery will be published
37 for installations that have been built against the Avahi client library.
39 Shares can be designated as a Time Machine share with the following setting:
41 'fruit:time machine = yes'
43 Support for lower casing the MDNS Name
44 ======================================
45 Allows the server name that is advertised through MDNS to be set to the
46 hostname rather than the Samba NETBIOS name. This allows an administrator
47 to make Samba registered MDNS records match the case of the hostname
48 rather than being in all capitals.
50 This can be set with the following settings:
56 Attributes deemed to be sensitive are now encrypted on disk. The sensitive
59 msDS-ExecuteScriptPassword
67 supplementalCredentials
73 This encryption is enabled by default on a new provision or join, it
74 can be disabled at provision or join time with the new option
77 However, an in-place upgrade will not encrypt the database.
79 Once encrypted, it is not possible to do an in-place downgrade (eg to
80 4.7) of the database. To obtain an unencrypted copy of the database a
81 new DC join should be performed, specifying the --plaintext-secrets
84 The key file "encrypted_secrets.key" is created in the same directory
85 as the database and should NEVER be disclosed. It is included by the
91 Parameter Name Description Default
92 -------------- ----------- -------
95 client schannel Default changed/ yes
97 gpo update command New
98 ldap ssl ads Deprecated
99 map untrusted to domain Removed
100 oplock contention limit Removed
101 prefork children New 1
102 mdns name Added netbios
103 fruit:time machine Added false
106 server schannel Default changed/ yes
109 winbind scan trusted domains New yes
110 winbind trusted domains only Removed
113 NT4-style replication based net commands removed
114 ================================================
116 The following commands and sub-commands have been removed from the
122 Also, replicating from a real NT4 domain with "net rpc vampire" and
123 "net rpc vampire keytab" has been removed.
125 The NT4-based commands were accidentially broken in 2013, and nobody
126 noticed the breakage. So instead of fixing them including tests (which
127 would have meant writing a server for the protocols, which we don't
128 have) we decided to remove them.
130 For the same reason, the "samsync", "samdeltas" and "database_redo"
131 commands have been removed from rpcclient.
133 "net rpc vampire keytab" from Active Directory domains continues to be
136 vfs_aio_linux module removed
137 ============================
139 The current Linux kernel aio does not match what Samba would
140 do. Shipping code that uses it leads people to false
141 assumptions. Samba implements async I/O based on threads by default,
142 there is no special module required to see benefits of read and write
143 request being sent do the disk in parallel.
145 smbclient reparse point symlink parameters reversed
146 ===================================================
148 A bug in smbclient caused the 'symlink' command to reverse the
149 meaning of the new name and link target parameters when creating a
150 reparse point symlink against a Windows server. As this is a
151 little used feature the ordering of these parameters has been
152 reversed to match the parameter ordering of the UNIX extensions
153 'symlink' command. The usage message for this command has also
154 been improved to remove confusion.
159 The dependency to global list of trusted domains within
160 the winbindd processes has been reduced a lot.
162 The construction of that global list is not reliable and often
163 incomplete in complex trust setups. In most situations the list is not needed
164 any more for winbindd to operate correctly. E.g. for plain file serving via SMB
165 using a simple idmap setup with autorid, tdb or ad. However some more complex
166 setups require the list, e.g. if you specify idmap backends for specific
167 domains. Some pam_winbind setups may also require the global list.
169 If you have a setup that doesn't require the global list, you should set
170 "winbind scan trusted domains = no".
175 The two commands "net serverid list" and "net serverid wipe" have been
176 removed, because the file serverid.tdb is not used anymore.
178 "net serverid list" can be replaced by listing all files in the
179 subdirectory "msg.lock" of Samba's "lock directory". The unique id
180 listed by "net serverid list" is stored in every process' lockfile in
183 "net serverid wipe" is not necessary anymore. It was meant primarily
184 for clustered environments, where the serverid.tdb file was not
185 properly cleaned up after single node crashes. Nowadays smbd and
186 winbind take care of cleaning up the msg.lock and msg.sock directories
192 https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.8#Release_blocking_bugs
195 #######################################
196 Reporting bugs & Development Discussion
197 #######################################
199 Please discuss this release on the samba-technical mailing list or by
200 joining the #samba-technical IRC channel on irc.freenode.net.
202 If you do report problems then please try to send high quality
203 feedback. If you don't provide vital information to help us track down
204 the problem then you will probably be ignored. All bug reports should
205 be filed under the Samba 4.1 and newer product in the project's Bugzilla
206 database (https://bugzilla.samba.org/).
209 ======================================================================
210 == Our Code, Our Bugs, Our Responsibility.
212 ======================================================================