4 This is the first release candidate of Samba 4.14. 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.14 will be the next version of the Samba suite.
18 The GPG release key for Samba releases changed from:
20 pub dsa1024/6F33915B6568B7EA 2007-02-04 [SC] [expires: 2021-02-05]
21 Key fingerprint = 52FB C0B8 6D95 4B08 4332 4CDC 6F33 915B 6568 B7EA
22 uid [ full ] Samba Distribution Verification Key <samba-bugs@samba.org>
23 sub elg2048/9C6ED163DA6DFB44 2007-02-04 [E] [expires: 2021-02-05]
25 to the following new key:
27 pub rsa4096/AA99442FB680B620 2020-12-21 [SC] [expires: 2022-12-21]
28 Key fingerprint = 81F5 E283 2BD2 545A 1897 B713 AA99 442F B680 B620
29 uid [ultimate] Samba Distribution Verification Key <samba-bugs@samba.org>
30 sub rsa4096/97EF9386FBFD4002 2020-12-21 [E] [expires: 2022-12-21]
32 Starting from Jan 21th 2021, all Samba releases will be signed with the new key.
34 See also GPG_AA99442FB680B620_replaces_6F33915B6568B7EA.txt
40 Here is a copy of a clarification note added to the Samba code
41 in the file: VFS-License-clarification.txt.
42 --------------------------------------------------------------
44 A clarification of our GNU GPL License enforcement boundary within the Samba
45 Virtual File System (VFS) layer.
47 Samba is licensed under the GNU GPL. All code committed to the Samba
48 project or that creates a "modified version" or software "based on" Samba must
49 be either licensed under the GNU GPL or a compatible license.
51 Samba has several plug-in interfaces where external code may be called
52 from Samba GNU GPL licensed code. The most important of these is the
55 Samba VFS modules are intimately connected by header files and API
56 definitions to the part of the Samba code that provides file services,
57 and as such, code that implements a plug-in Samba VFS module must be
58 licensed under the GNU GPL or a compatible license.
60 However, Samba VFS modules may themselves call third-party external
61 libraries that are not part of the Samba project and are externally
62 developed and maintained.
64 As long as these third-party external libraries do not use any of the
65 Samba internal structure, APIs or interface definitions created by the
66 Samba project (to the extent that they would be considered subject to the GNU
67 GPL), then the Samba Team will not consider such third-party external
68 libraries called from Samba VFS modules as "based on" and/or creating a
69 "modified version" of the Samba code for the purposes of GNU GPL.
70 Accordingly, we do not require such libraries be licensed under the GNU GPL
71 or a GNU GPL compatible license.
76 The effort to modernize Samba's VFS interface has reached a major milestone with
77 the next release Samba 4.14.
79 For details please refer to the documentation at source3/modules/The_New_VFS.txt or
80 visit the <https://wiki.samba.org/index.php/The_New_VFS>.
85 Publishing printers in AD is more reliable and more printer features are
86 added to the published information in AD. Samba now also supports Windows
87 drivers for the ARM64 architecture.
92 This release extends Samba to support Group Policy functionality for Winbind
93 clients. Active Directory Administrators can set policies that apply Sudoers
94 configuration, and cron jobs to run hourly, daily, weekly or monthly.
96 To enable the application of Group Policies on a client, set the global
97 smb.conf option 'apply group policies' to 'yes'. Policies are applied on an
98 interval of every 90 minutes, plus a random offset between 0 and 30 minutes.
100 Policies applied by Samba are 'non-tattooing', meaning that changes can be
101 reverted by executing the `samba-gpupdate --unapply` command. Policies can be
102 re-applied using the `samba-gpupdate --force` command.
103 To view what policies have been or will be applied to a system, use the
104 `samba-gpupdate --rsop` command.
106 Administration of Samba policy requires that a Samba ADMX template be uploaded
107 to the SYSVOL share. The samba-tool command `samba-tool gpo admxload` is
108 provided as a convenient method for adding this policy. Once uploaded, policies
109 can be modified in the Group Policy Management Editor under Computer
110 Configuration/Policies/Administrative Templates. Alternatively, Samba policy
111 may be managed using the `samba-tool gpo manage` command. This tool does not
112 require the admx templates to be installed.
115 Python 3.6 or later required
116 ----------------------------
118 Samba's minimum runtime requirement for python was raised to Python
119 3.6 with samba 4.13. Samba 4.14 raises this minimum version to Python
120 3.6 also to build Samba. It is no longer possible to build Samba
121 (even just the file server) with Python versions 2.6 and 2.7.
123 As Python 2.7 has been End Of Life upstream since April 2020, Samba
124 is dropping ALL Python 2.x support in this release.
127 NT4-like 'classic' Samba domain controllers
128 -------------------------------------------
130 Samba 4.13 deprecates Samba's original domain controller mode.
132 Sites using Samba as a Domain Controller should upgrade from the
133 NT4-like 'classic' Domain Controller to a Samba Active Directory DC
134 to ensure full operation with modern windows clients.
137 SMBv1 only protocol options deprecated
138 --------------------------------------
140 A number of smb.conf parameters for less-secure authentication methods
141 which are only possible over SMBv1 are deprecated in this release.
144 Miscellaneous samba-tool changes
145 --------------------------------
147 The samba-tool commands to manage AD objects (e.g. users, computers and
148 groups) now consistently use the "add" command when adding a new object to
149 the AD. The previous deprecation warnings when using the "add" commands
150 have been removed. For compatibility reasons, both the "add" and "create"
151 commands can be used now.
153 Users, groups and contacts can now be renamed with the respective rename
156 Locked users can be unlocked with the new "samba-tool user unlock" command.
158 The "samba-tool user list" and "samba-tool group listmembers" commands
159 provide additional options to hide expired and disabled user accounts
160 (--hide-expired and --hide-disabled).
166 * The NAT gateway and LVS features now uses the term "leader" to refer
167 to the main node in a group through which traffic is routed and
168 "follower" for other members of a group. The command for
169 determining the leader has changed to "ctdb natgw leader" (from
170 "ctdb natgw master"). The configuration keyword for indicating that
171 a node can not be the leader of a group has changed to
172 "follower-only" (from "slave-only"). Identical changes were made
175 * Remove "ctdb isnotrecmaster" command. It isn't used by CTDB's
176 scripts and can be checked by users with "ctdb pnn" and "ctdb
183 The deprecated "ldap ssl ads" smb.conf option has been removed.
189 Parameter Name Description Default
190 -------------- ----------- -------
193 client plaintext auth Deprecated no
194 client NTLMv2 auth Deprecated yes
195 client lanman auth Deprecated no
196 client use spnego Deprecated yes
197 domain logons Deprecated no
198 raw NTLMv2 auth Deprecated no
199 async dns timeout New 10
200 client smb encrypt New default
201 honor change notify privilege New No
202 smbd force process locks New No
203 server smb encrypt New default
209 https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.14#Release_blocking_bugs
212 #######################################
213 Reporting bugs & Development Discussion
214 #######################################
216 Please discuss this release on the samba-technical mailing list or by
217 joining the #samba-technical IRC channel on irc.freenode.net.
219 If you do report problems then please try to send high quality
220 feedback. If you don't provide vital information to help us track down
221 the problem then you will probably be ignored. All bug reports should
222 be filed under the Samba 4.1 and newer product in the project's Bugzilla
223 database (https://bugzilla.samba.org/).
226 ======================================================================
227 == Our Code, Our Bugs, Our Responsibility.
229 ======================================================================