4 This is the first preview release of Samba 4.12. 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.12 will be the next version of the Samba suite.
22 Samba's minimum runtime requirement for python was raised to Python
23 3.4 with samba 4.11. Samba 4.12 raises this minimum version to Python
24 3.5 both to access new features and because this is the oldest version
25 we test with in our CI infrastructure.
27 (Build time support for the file server with Python 2.6 has not
33 Samba is making efforts to remove in-tree cryptographic functionality,
34 and to instead rely on externally maintained libraries. To this end,
35 Samba has chosen GnuTLS as our standard cryptographic provider.
37 Samba now requires GnuTLS 3.4.7 to be installed (including development
38 headers at build time) for all configurations, not just the Samba AD
41 Using GnuTLS for SMB3 encryption you will notice huge performance and copy
42 speed improvements. Tests with the CIFS Kernel client from Linux Kernel 5.3
43 show a 3x speed improvement for writing and a 2.5x speed improvement for reads!
45 NOTE WELL: The use of GnuTLS means that Samba will honour the
46 system-wide 'FIPS mode' (a reference to the US FIPS-140 cryptographic
47 standard) and so will not operate in many still common situations if
48 this system-wide parameter is in effect, as many of our protocols rely
49 on outdated cryptography.
51 A future Samba version will mitigate this to some extent where good
52 cryptography effectively wraps bad cryptography, but for now that above
59 The smb.conf parameter "write cache size" has been removed.
61 Since the in-memory write caching code was written, our write path has
62 changed significantly. In particular we have gained very flexible
63 support for async I/O, with the new linux io_uring interface in
64 development. The old write cache concept which cached data in main
65 memory followed by a blocking pwrite no longer gives any improvement
66 on modern systems, and may make performance worse on memory-contrained
67 systems, so this functionality should not be enabled in core smbd
70 In addition, it complicated the write code, which is a performance
73 If required for specialist purposes, it can be recreated as a VFS
76 BIND9_FLATFILE deprecated
77 -------------------------
79 The BIND9_FLATFILE DNS backend is deprecated in this release and will
80 be removed in the future. This was only practically useful on a single
81 domain controller or under expert care and supervision.
83 This release removes the "rndc command" smb.conf parameter, which
84 supported this configuration by writing out a list of DCs permitted to
85 make changes to the DNS Zone and nudging the 'named' server if a new
86 DC was added to the domain. Administrators using BIND9_FLATFILE will
87 need to maintain this manually from now on.
92 Parameter Name Description Default
93 -------------- ----------- -------
95 nfs4:acedup Changed default merge
97 write cache size Removed
102 https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.12#Release_blocking_bugs
105 #######################################
106 Reporting bugs & Development Discussion
107 #######################################
109 Please discuss this release on the samba-technical mailing list or by
110 joining the #samba-technical IRC channel on irc.freenode.net.
112 If you do report problems then please try to send high quality
113 feedback. If you don't provide vital information to help us track down
114 the problem then you will probably be ignored. All bug reports should
115 be filed under the Samba 4.1 and newer product in the project's Bugzilla
116 database (https://bugzilla.samba.org/).
119 ======================================================================
120 == Our Code, Our Bugs, Our Responsibility.
122 ======================================================================