4 This is the first preview release of Samba 4.7. 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.7 will be the next version of the Samba suite.
18 smbclient no longer prints a 'Domain=[...] OS=[Windows 6.1] Server=[...]'
19 banner when connecting to the first server. With SMB2 and Kerberos
20 there's no way to print this information reliable. Now we avoid it at all
21 consistently. In interactive session the following banner is now presented
22 to the user: 'Try "help" do get a list of possible commands.'.
28 Samba AD with MIT Kerberos
29 --------------------------
31 After four years of development, Samba finally supports compiling and
32 running Samba AD with MIT Kerberos. You can enable it with:
34 ./configure --with-system-mitkrb5
36 Samba requires version 1.15.1 of MIT Kerberos to build with AD DC support.
37 The krb5-devel and krb5-server packages are required.
38 The feature set is not on par with with the Heimdal build but the most important
39 things, like forest and external trusts, are working. Samba uses the KDC binary
40 provided by MIT Kerberos.
42 Missing features, compared to Heimdal, are:
44 * S4U2SELF/S4U2PROXY support
45 * RODC support (not fully working with Heimdal either)
47 The Samba AD process will take care of starting the MIT KDC and it will load a
48 KDB (Kerberos Database) driver to access the Samba AD database. When
49 provisioning an AD DC using 'samba-tool' it will take care of creating a correct
50 kdc.conf file for the MIT KDC. Note that 'samba-tool' will overwrite the system
51 kdc.conf by default. It is possible to use a different location during
52 provision. You should consult the 'samba-tool' help and smb.conf manpage for
55 Dynamic RPC port range
56 ----------------------
58 The dynamic port range for RPC services has been changed from the old default
59 value 1024-1300 to 49152-65535. This port range is not only used by a
60 Samba AD DC but also applies to all other server roles including NT4-style
61 domain controllers. The new value has been defined by Microsoft in Windows
62 Server 2008 and newer versions. To make it easier for Administrators to control
63 those port ranges we use the same default and make it configurable with the
64 option: 'rpc server dynamic port range'.
66 The 'rpc server port' option sets the first available port from the new
67 'rpc server dynamic port range' option. The option 'rpc server port' only
68 applies to Samba provisioned as an AD DC.
70 Authentication and Authorization audit support
71 ----------------------------------------------
73 Detailed authentication and authorization audit information is now
74 logged to Samba's debug logs under the "auth_audit" debug class,
75 including in particular the client IP address triggering the audit
76 line. Additionally, if Samba is compiled against the jansson JSON
77 library, a JSON representation is logged under the "auth_json_audit"
80 Audit support is comprehensive for all authentication and
81 authorisation of user accounts in the Samba Active Directory Domain
82 Controller, as well as the implicit authentication in password
83 changes. In the file server and classic/NT4 domain controller, NTLM
84 authentication, SMB and RPC authorization is covered, however password
85 changes are not at this stage, and this support is not currently
86 backed by a testsuite.
88 Query record for open file or directory
89 ---------------------------------------
91 The record attached to an open file or directory in Samba can be
92 queried through the 'net tdb locking' command. In clustered Samba this
93 can be useful to determine the file or directory triggering
94 corresponding "hot" record warnings in ctdb.
96 Removal of lpcfg_register_defaults_hook()
97 -----------------------------------------
99 The undocumented and unsupported function lpcfg_register_defaults_hook()
100 that was used by external projects to call into Samba and modify
101 smb.conf default parameter settings has been removed. If your project
102 was using this call please raise the issue on
103 samba-technical@lists.samba.org in order to design a supported
104 way of obtaining the same functionality.
106 Change of loadable module interface
107 -----------------------------------
109 The _init function of all loadable modules in Samba has changed
112 NTSTATUS _init(void);
116 NTSTATUS _init(TALLOC_CTX *);
118 This allows a program loading a module to pass in a long-lived
119 talloc context (which must be guaranteed to be alive for the
120 lifetime of the module). This allows modules to avoid use of
121 the talloc_autofree_context() (which is inherently thread-unsafe)
122 and still be valgrind-clean on exit. Modules that don't need to
123 free long-lived data on exist should use the NULL talloc context.
128 The "strict sync" global parameter has been changed from
129 a default of "no" to "yes". This means smbd will by default
130 obey client requests to synchronize unwritten data in operating
131 system buffers safely onto disk. This is a safer default setting
132 for modern SMB1/2/3 clients.
137 Parameter Name Description Default
138 -------------- ----------- -------
139 allow unsafe cluster upgrade New parameter no
140 auth event notification New parameter no
141 auth methods Deprecated
142 map untrusted to domain New value/ auto
145 mit kdc command New parameter
146 profile acls Deprecated
147 rpc server dynamic port range New parameter 49152-65535
148 strict sync Default changed yes
154 https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.7#Release_blocking_bugs
157 #######################################
158 Reporting bugs & Development Discussion
159 #######################################
161 Please discuss this release on the samba-technical mailing list or by
162 joining the #samba-technical IRC channel on irc.freenode.net.
164 If you do report problems then please try to send high quality
165 feedback. If you don't provide vital information to help us track down
166 the problem then you will probably be ignored. All bug reports should
167 be filed under the Samba 4.1 and newer product in the project's Bugzilla
168 database (https://bugzilla.samba.org/).
171 ======================================================================
172 == Our Code, Our Bugs, Our Responsibility.
174 ======================================================================