4 This is the first pre release 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.
19 Here is a copy of a clarification note added to the Samba code
20 in the file: VFS-License-clarification.txt.
21 --------------------------------------------------------------
23 A clarification of our GNU GPL License enforcement boundary within the Samba
24 Virtual File System (VFS) layer.
26 Samba is licensed under the GNU GPL. All code committed to the Samba
27 project or that creates a "modified version" or software "based on" Samba must
28 be either licensed under the GNU GPL or a compatible license.
30 Samba has several plug-in interfaces where external code may be called
31 from Samba GNU GPL licensed code. The most important of these is the
34 Samba VFS modules are intimately connected by header files and API
35 definitions to the part of the Samba code that provides file services,
36 and as such, code that implements a plug-in Samba VFS module must be
37 licensed under the GNU GPL or a compatible license.
39 However, Samba VFS modules may themselves call third-party external
40 libraries that are not part of the Samba project and are externally
41 developed and maintained.
43 As long as these third-party external libraries do not use any of the
44 Samba internal structure, APIs or interface definitions created by the
45 Samba project (to the extent that they would be considered subject to the GNU
46 GPL), then the Samba Team will not consider such third-party external
47 libraries called from Samba VFS modules as "based on" and/or creating a
48 "modified version" of the Samba code for the purposes of GNU GPL.
49 Accordingly, we do not require such libraries be licensed under the GNU GPL
50 or a GNU GPL compatible license.
56 Publishing printers in AD is more reliable and more printer features are
57 added to the published information in AD. Samba now also supports Windows
58 drivers for the ARM64 architecture.
63 This release extends Samba to support Group Policy functionality for Winbind
64 clients. Active Directory Administrators can set policies that apply Sudoers
65 configuration, and cron jobs to run hourly, daily, weekly or monthly.
67 To enable the application of Group Policies on a client, set the global
68 smb.conf option 'apply group policies' to 'yes'. Policies are applied on an
69 interval of every 90 minutes, plus a random offset between 0 and 30 minutes.
71 Policies applied by Samba are 'non-tattooing', meaning that changes can be
72 reverted by executing the `samba-gpupdate --unapply` command. Policies can be
73 re-applied using the `samba-gpupdate --force` command.
74 To view what policies have been or will be applied to a system, use the
75 `samba-gpupdate --rsop` command.
77 Administration of Samba policy requires that a Samba ADMX template be uploaded
78 to the SYSVOL share. The samba-tool command `samba-tool gpo admxload` is
79 provided as a convenient method for adding this policy. Once uploaded, policies
80 can be modified in the Group Policy Management Editor under Computer
81 Configuration/Policies/Administrative Templates. Alternatively, Samba policy
82 may be managed using the `samba-tool gpo manage` command. This tool does not
83 require the admx templates to be installed.
88 * The NAT gateway and LVS features now uses the term "leader" to refer
89 to the main node in a group through which traffic is routed and
90 "follower" for other members of a group. The command for
91 determining the leader has changed to "ctdb natgw leader" (from
92 "ctdb natgw master"). The configuration keyword for indicating that
93 a node can not be the leader of a group has changed to
94 "follower-only" (from "slave-only"). Identical changes were made
97 * Remove "ctdb isnotrecmaster" command. It isn't used by CTDB's
98 scripts and can be checked by users with "ctdb pnn" and "ctdb
101 Python 3.6 or later required
102 ----------------------------
104 Samba's minimum runtime requirement for python was raised to Python
105 3.6 with samba 4.13. Samba 4.14 raises this minimum version to Python
106 3.6 also to build Samba. It is no longer possible to build Samba
107 (even just the file server) with Python versions 2.6 and 2.7.
109 As Python 2.7 has been End Of Life upstream since April 2020, Samba
110 is dropping ALL Python 2.x support in this release.
113 NT4-like 'classic' Samba domain controllers
114 -------------------------------------------
116 Samba 4.13 deprecates Samba's original domain controller mode.
118 Sites using Samba as a Domain Controller should upgrade from the
119 NT4-like 'classic' Domain Controller to a Samba Active Directory DC
120 to ensure full operation with modern windows clients.
122 SMBv1 only protocol options deprecated
123 --------------------------------------
125 A number of smb.conf parameters for less-secure authentication methods
126 which are only possible over SMBv1 are deprecated in this release.
131 The deprecated "ldap ssl ads" smb.conf option has been removed.
136 Parameter Name Description Default
137 -------------- ----------- -------
140 client plaintext auth Deprecated no
141 client NTLMv2 auth Deprecated yes
142 client lanman auth Deprecated no
143 client use spnego Deprecated yes
144 domain logons Deprecated no
145 raw NTLMv2 auth Deprecated no
146 async dns timeout New 10
147 client smb encrypt New default
148 honor change notify privilege New No
149 smbd force process locks New No
150 server smb encrypt New default
157 https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.14#Release_blocking_bugs
160 #######################################
161 Reporting bugs & Development Discussion
162 #######################################
164 Please discuss this release on the samba-technical mailing list or by
165 joining the #samba-technical IRC channel on irc.freenode.net.
167 If you do report problems then please try to send high quality
168 feedback. If you don't provide vital information to help us track down
169 the problem then you will probably be ignored. All bug reports should
170 be filed under the Samba 4.1 and newer product in the project's Bugzilla
171 database (https://bugzilla.samba.org/).
174 ======================================================================
175 == Our Code, Our Bugs, Our Responsibility.
177 ======================================================================