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.
23 Samba is making efforts to remove in-tree cryptographic functionality,
24 and to instead rely on externally maintained libraries. To this end,
25 Samba has chosen GnuTLS as our standard cryptographic provider.
27 Samba now requires GnuTLS 3.4.7 to be installed (including development
28 headers at build time) for all configurations, not just the Samba AD
31 NOTE WELL: The use of GnuTLS means that Samba will honour the
32 system-wide 'FIPS mode' (a reference to the US FIPS-140 cryptographic
33 standard) and so will not operate in many still common situations if
34 this system-wide parameter is in effect, as many of our protocols rely
35 on outdated cryptography.
37 A future Samba version will mitigate this to some extent where good
38 cryptography effectively wraps bad cryptography, but for now that above
45 BIND9_FLATFILE deprecated
46 -------------------------
48 The BIND9_FLATFILE DNS backend is deprecated in this release and will
49 be removed in the future. This was only practically useful on a single
50 domain controller or under expert care and supervision.
52 This release removes the "rndc command" smb.conf parameter, which
53 supported this configuration by writing out a list of DCs permitted to
54 make changes to the DNS Zone and nudging the 'named' server if a new
55 DC was added to the domain. Administrators using BIND9_FLATFILE will
56 need to maintain this manually from now on.
61 Parameter Name Description Default
62 -------------- ----------- -------
64 nfs4:acedup Changed default merge
70 https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.12#Release_blocking_bugs
73 #######################################
74 Reporting bugs & Development Discussion
75 #######################################
77 Please discuss this release on the samba-technical mailing list or by
78 joining the #samba-technical IRC channel on irc.freenode.net.
80 If you do report problems then please try to send high quality
81 feedback. If you don't provide vital information to help us track down
82 the problem then you will probably be ignored. All bug reports should
83 be filed under the Samba 4.1 and newer product in the project's Bugzilla
84 database (https://bugzilla.samba.org/).
87 ======================================================================
88 == Our Code, Our Bugs, Our Responsibility.
90 ======================================================================