1 What's new in Samba 4 alpha20
2 =============================
4 Samba 4.0 will be the next version of the Samba suite and incorporates
5 all the technology found in both the Samba4 alpha series and the
6 stable 3.x series. The primary additional features over Samba 3.6 are
7 support for the Active Directory logon protocols used by Windows 2000
13 This is a security release in order to address CVE-2012-2111
14 (Incorrect permission checks when granting/removing privileges can
15 compromise file server security).
18 Samba 3.4.x to 3.6.4 are affected by a
19 vulnerability that allows arbitrary users
20 to modify privileges on a file server.
22 This is in regards to the smbd file server, which is shipped in Samba
23 4.0 alpha. The AD DC is not directly impacted, as the LSA
24 implementation differs.
29 Samba4 alpha20 is not a final Samba release, however we are now making
30 good progress towards a Samba 4.0 release, of which this is a preview.
31 Be aware the this release contains both the technology of Samba 3.6
32 (that you can reasonably expect to upgrade existing Samba 3.x releases
33 to) and the AD domain controller work previously known as 'samba4'.
35 While binaries for the stable file server are provided in this
36 release, for a stable, supported file server, Samba3 domain or AD
37 domain member installation, please run a Samba 3.x release, as we are
38 still bedding down the new single build system.
40 Samba4 is subjected to an awesome battery of tests on an automated
41 basis, we have found Samba 4.0 to be very stable in it's behavior.
42 However, we still recommend against upgrading production servers from
43 Samba 3.x release to Samba 4.0 alpha at this stage.
45 If you are upgrading, or looking to develop, test or deploy Samba 4.0
46 alpha releases, you should backup all configuration and data.
51 Samba 4.0 alpha supports the server-side of the Active Directory logon
52 environment used by Windows 2000 and later, so we can do full domain
53 join and domain logon operations with these clients.
55 Our Domain Controller (DC) implementation includes our own built-in
56 LDAP server and Kerberos Key Distribution Center (KDC) as well as the
57 Samba3-like logon services provided over CIFS. We correctly generate
58 the infamous Kerberos PAC, and include it with the Kerberos tickets we
61 Samba 4.0 alpha ships with two distinct file servers. The file server
62 from the Samba 3.x series is 'smbd', and works with the binaries users
63 would expect from that series (nmbd, winbindd, smbpasswd).
65 Samba 4.0 also ships with a new file server, which is tuned to match
66 the requirements of an AD domain controller. Users should not use the
67 file server in the 'samba' binary for non-DC related tasks.
69 A new scripting interface has been added to Samba 4, allowing Python
70 programs to interface to Samba's internals, and many tools and
71 internal workings of the DC code is now implemented in python.
77 For a list of changes since alpha 19, please see the git log.
79 $ git clone git://git.samba.org/samba.git
81 $ git log samba-4.0.0alpha19..samba-4.0.0alpha20
83 Some major user-visible changes include:
85 Improvements to the 'samba-tool domain samba3upgrade' and
86 samba_upgradedns tools
88 Stability improvements in the Samba4 winbind implementation (that
89 used in the AD DC mode).
91 The BIND 9 DLZ plugin is now compatible with both BIND 9.8, and BIND 9.9.
93 dbcheck and runtime protection for the fSMORoleOwner attribute. This
94 allows us to recover from a situation where the fSMORoleOwner is
97 Support for storing the posixAccount and other auxiliary objectClass
98 values (the values are not used by Samba as an AD DC at this stage,
99 but may be used by clients).
102 Some major but less visible changes include:
104 Continued early implementation work on the SMB 2.2 protocol client and server as
105 the team improves and develops support these new protocols.
107 Initial work to build Samba using MIT kerberos in the top level waf
108 build system. This is not complete at this time, but good progress is
115 - upgradeprovision should not be run when upgrading to this release
116 from a recent release. No important database format changes have
117 been made since alpha16.
119 - Installation on systems without a system iconv (and developer
120 headers at compile time) is known to cause errors when dealing with
121 non-ASCII characters.
123 - In some situations, group members may not be upgraded by the
124 samba-tool domain samba3upgrade tool
126 - Domain member support in the 'samba' binary is in it's infancy, and
127 is not comparable to the support found in winbindd. As such, do not
128 use the 'samba' binary (provided for the AD server) on a member
131 - There is no printing support in the 'samba' binary (use smbd instead)
133 - There is no NetBIOS browsing support (network neighbourhood) in the
134 'samba' binary (use nmbd and smbd instead)
136 - Clock Synchronisation is critical. Many 'wrong password' errors are
137 actually due to Kerberos objecting to a clock skew between client
138 and server. (The NTP work in the previous alphas are partly to assist
141 - The DRS replication code may fail. Please contact the team if you
142 experience issues with DRS replication, as we have fixed many issues
143 here in response to feedback from our production users.
145 RUNNING Samba 4.0 as an AD DC
146 =============================
148 A short guide to setting up Samba 4 as an AD DC can be found on the wiki:
150 http://wiki.samba.org/index.php/Samba4/HOWTO
152 #######################################
153 Reporting bugs & Development Discussion
154 #######################################
156 Please discuss this release on the samba-technical mailing list or by
157 joining the #samba-technical IRC channel on irc.freenode.net.
159 If you do report problems then please try to send high quality
160 feedback. If you don't provide vital information to help us track down
161 the problem then you will probably be ignored. All bug reports should
162 be filed under the Samba 4.0 product in the project's Bugzilla
163 database (https://bugzilla.samba.org/).
166 ======================================================================
167 == Our Code, Our Bugs, Our Responsibility.
169 ======================================================================