[ANNOUNCE] Samba 4.0 alpha 20 for CCVE-2012-2111
abartlet at samba.org
Tue May 1 04:04:09 MDT 2012
We are proud to a announce another alpha release of Samba 4.0, alpha 20
THIS IS A SECURITY RELEASE for CVE-2012-2111, which impacts on users
running the smbd file server from Samba4 alpha releases, but not users
running the AD Domain Controller.
What's new in Samba 4 alpha20
Samba 4.0 will be the next version of the Samba suite and incorporates
all the technology found in both the Samba4 alpha series and the
stable 3.x series. The primary additional features over Samba 3.6 are
support for the Active Directory logon protocols used by Windows 2000
This is a security release in order to address CVE-2012-2111
(Incorrect permission checks when granting/removing privileges can
compromise file server security).
Samba 3.4.x to 3.6.4 are affected by a
vulnerability that allows arbitrary users
to modify privileges on a file server.
This is in regards to the smbd file server, which is shipped in Samba
4.0 alpha. The AD DC is not directly impacted, as the LSA
Samba4 alpha20 is not a final Samba release, however we are now making
good progress towards a Samba 4.0 release, of which this is a preview.
Be aware the this release contains both the technology of Samba 3.6
(that you can reasonably expect to upgrade existing Samba 3.x releases
to) and the AD domain controller work previously known as 'samba4'.
While binaries for the stable file server are provided in this
release, for a stable, supported file server, Samba3 domain or AD
domain member installation, please run a Samba 3.x release, as we are
still bedding down the new single build system.
Samba4 is subjected to an awesome battery of tests on an automated
basis, we have found Samba 4.0 to be very stable in it's behavior.
However, we still recommend against upgrading production servers from
Samba 3.x release to Samba 4.0 alpha at this stage.
If you are upgrading, or looking to develop, test or deploy Samba 4.0
alpha releases, you should backup all configuration and data.
Samba 4.0 alpha supports the server-side of the Active Directory logon
environment used by Windows 2000 and later, so we can do full domain
join and domain logon operations with these clients.
Our Domain Controller (DC) implementation includes our own built-in
LDAP server and Kerberos Key Distribution Center (KDC) as well as the
Samba3-like logon services provided over CIFS. We correctly generate
the infamous Kerberos PAC, and include it with the Kerberos tickets we
Samba 4.0 alpha ships with two distinct file servers. The file server
from the Samba 3.x series is 'smbd', and works with the binaries users
would expect from that series (nmbd, winbindd, smbpasswd).
Samba 4.0 also ships with a new file server, which is tuned to match
the requirements of an AD domain controller. Users should not use the
file server in the 'samba' binary for non-DC related tasks.
A new scripting interface has been added to Samba 4, allowing Python
programs to interface to Samba's internals, and many tools and
internal workings of the DC code is now implemented in python.
CHANGES SINCE alpha19
For a list of changes since alpha 19, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
$ git log samba-4.0.0alpha19..samba-4.0.0alpha20
Some major user-visible changes include:
Improvements to the 'samba-tool domain samba3upgrade' and
Stability improvements in the Samba4 winbind implementation (that
used in the AD DC mode).
The BIND 9 DLZ plugin is now compatible with both BIND 9.8, and BIND 9.9.
dbcheck and runtime protection for the fSMORoleOwner attribute. This
allows us to recover from a situation where the fSMORoleOwner is
Support for storing the posixAccount and other auxiliary objectClass
values (the values are not used by Samba as an AD DC at this stage,
but may be used by clients).
Some major but less visible changes include:
Continued early implementation work on the SMB 2.2 protocol client and server as
the team improves and develops support these new protocols.
Initial work to build Samba using MIT kerberos in the top level waf
build system. This is not complete at this time, but good progress is
- upgradeprovision should not be run when upgrading to this release
from a recent release. No important database format changes have
been made since alpha16.
- Installation on systems without a system iconv (and developer
headers at compile time) is known to cause errors when dealing with
- In some situations, group members may not be upgraded by the
samba-tool domain samba3upgrade tool
- Domain member support in the 'samba' binary is in it's infancy, and
is not comparable to the support found in winbindd. As such, do not
use the 'samba' binary (provided for the AD server) on a member
- There is no printing support in the 'samba' binary (use smbd instead)
- There is no NetBIOS browsing support (network neighbourhood) in the
'samba' binary (use nmbd and smbd instead)
- Clock Synchronisation is critical. Many 'wrong password' errors are
actually due to Kerberos objecting to a clock skew between client
and server. (The NTP work in the previous alphas are partly to assist
with this problem).
- The DRS replication code may fail. Please contact the team if you
experience issues with DRS replication, as we have fixed many issues
here in response to feedback from our production users.
RUNNING Samba 4.0 as an AD DC
A short guide to setting up Samba 4 as an AD DC can be found on the wiki:
Reporting bugs & Development Discussion
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.freenode.net.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
be filed under the Samba 4.0 product in the project's Bugzilla
== Our Code, Our Bugs, Our Responsibility.
== The Samba Team
The release tarball is available from the following location:
This release has been signed using GPG with Andrew's GPG key 28B436BB).
To verify that the signature is correct, make sure that the tarball has
been unzipped and run:
$ gpg --verify samba-4.0.0alpha20.tar.asc
The Samba team
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
More information about the samba-technical