1 What's new in Samba 4 alpha5
2 ============================
4 Samba 4 is the ambitious next version of the Samba suite that is being
5 developed in parallel to the stable 3.0 series. The main emphasis in
6 this branch is support for the Active Directory logon protocols used
7 by Windows 2000 and above.
9 Samba4 alpha5 follows on from the alpha release series we have been
10 publishing since September 2007
15 Samba4 alpha5 is not a final Samba release. That is more a reference
16 to Samba4's lack of the features we expect you will need than a
17 statement of code quality, but clearly it hasn't seen a broad
18 deployment yet. If you were to upgrade Samba3 (or indeed Windows) to
19 Samba4, you would find many things work, but that other key features
20 you may have relied on simply are not there yet.
22 For example, while Samba 3.0 is an excellent member of a Active
23 Directory domain, Samba4 is happier as a domain controller, and it is
24 in this role where it has seen deployment into production.
26 Samba4 is subjected to an awesome battery of tests on an
27 automated basis, we have found Samba4 to be very stable in it's
28 behaviour. We have to recommend against upgrading production servers
29 from Samba 3 to Samba 4 at this stage, because there may be the features on
30 which you may rely that are not present, or the mapping of
31 your configuration and user database may not be complete.
33 If you are upgrading, or looking to develop, test or deploy Samba4, you should
34 backup all configuration and data.
39 Samba4 supports the server-side of the Active Directory logon environment
40 used by Windows 2000 and later, so we can do full domain join
41 and domain logon operations with these clients.
43 Our Domain Controller (DC) implementation includes our own built-in
44 LDAP server and Kerberos Key Distribution Center (KDC) as well as the
45 Samba3-like logon services provided over CIFS. We correctly generate
46 the infamous Kerberos PAC, and include it with the Kerberos tickets we
49 The new VFS features in Samba 4 adapts the filesystem on the server to
50 match the Windows client semantics, allowing Samba 4 to better match
51 windows behaviour and application expectations. This includes file
52 annotation information (in streams) and NT ACLs in particular. The
53 VFS is backed with an extensive automated test suite.
55 A new scripting interface has been added to Samba 4, allowing
56 Python programs to interface to Samba's internals.
58 The Samba 4 architecture is based around an LDAP-like database that
59 can use a range of modular backends. One of the backends supports
60 standards compliant LDAP servers (including OpenLDAP), and we are
61 working on modules to map between AD-like behaviours and this backend.
62 We are aiming for Samba 4 to be powerful frontend to large
68 In the time since Samba4 Alpha4 was released in June 2008, Samba has
69 continued to evolve, but you may particularly notice these areas:
71 LDAP backend support restored (issues preventing the use of the LDAP
72 backend in alpha4 have been addressed).
74 SMB2 Support: The SMB2 server, while still disabled, has improved,
75 and now supports SMB2 signing.
77 OpenChange support: Updates have been made since alpha4 to better
78 support OpenChange's use of Samba4's libraries.
80 Faster ldb loading: A fix to avoid calling 'init_module' (which was
81 not defined by Samba modules, but was by the C library) will fix
82 some of the slowness in authentication.
84 SWAT Remains Disabled: Due to a lack of developer time and without a
85 long-term web developer to maintain it, the SWAT web UI remains been
86 disabled (and would need to be rewritten in python in any case).
88 GNU Make: To try and simplfy our build system, we rely on GNU Make
89 to avoid autogenerating a massive single makefile.
92 These are just some of the highlights of the work done in the past few
93 months. More details can be found in our GIT history.
99 Those familiar with Samba 3 can find a list of user-visible changes
100 since that release series in the NEWS file.
105 - Domain member support is in it's infancy, and is not comparable to
106 the support found in Samba3.
108 - There is no printing support in the current release.
110 - There is no NetBIOS browsing support in the current release
112 - The Samba4 port of the CTDB clustering support is not yet complete
114 - Clock Synchronisation is critical. Many 'wrong password' errors are
115 actually due to Kerberos objecting to a clock skew between client
116 and server. (The NTP work in the previous alpha is partly to assist
119 - Samba4 alpha5 is currently only portable to recent Linux
120 distributions. Work to return support for other Unix varients is
121 expected during the next alpha cycle
123 - Samba4 alpha5 is incompatible with GnuTLS 2.0, found in Fedora 9 and
124 recent Ubuntu releases. GnuTLS use may be disabled using the
125 --disable-gnutls argument to ./configure. (otherwise 'make test' and
126 LDAPS operations will hang).
131 A short guide to setting up Samba 4 can be found in the howto.txt file
132 in root of the tarball.
134 DEVELOPMENT and FEEDBACK
135 ========================
136 Bugs can be filed at https://bugzilla.samba.org/ but please be aware
137 that many features are simply not expected to work at this stage.
139 The Samba Wiki at http://wiki.samba.org should detail some of these
142 Development and general discussion about Samba 4 happens mainly on
143 the #samba-technical IRC channel (on irc.freenode.net) and
144 the samba-technical mailing list (see http://lists.samba.org/ for