-What's new in Samba 4 alpha4
+What's new in Samba 4 alpha5
============================
Samba 4 is the ambitious next version of the Samba suite that is being
this branch is support for the Active Directory logon protocols used
by Windows 2000 and above.
-Samba 4 is currently not yet in a state where it is usable in
-production environments. Note the WARNINGS below, and the STATUS file,
-which aims to document what should and should not work.
-
-Samba4 alpha4 follows on from the alpha release series we have been
-publishing since September last year.
+Samba4 alpha5 follows on from the alpha release series we have been
+publishing since September 2007
WARNINGS
========
-Samba4 alpha4 is not a final Samba release. That is more a reference
+Samba4 alpha5 is not a final Samba release. That is more a reference
to Samba4's lack of the features we expect you will need than a
statement of code quality, but clearly it hasn't seen a broad
deployment yet. If you were to upgrade Samba3 (or indeed Windows) to
you may have relied on simply are not there yet.
For example, while Samba 3.0 is an excellent member of a Active
-Directory domain, Samba4 is happier as a domain controller: (This is
-where we have done most of the research and development).
-
-While Samba4 is subjected to an awesome battery of tests on an
-automated basis, and we have found Samba4 to be very stable in it's
-behaviour, we have to recommend against upgrading production servers
-from Samba 3 to Samba 4 at this stage. If you are upgrading an
-experimental server, or looking to develop and test Samba, you should
+Directory domain, Samba4 is happier as a domain controller, and it is
+in this role where it has seen deployment into production.
+
+Samba4 is subjected to an awesome battery of tests on an
+automated basis, we have found Samba4 to be very stable in it's
+behaviour. We have to recommend against upgrading production servers
+from Samba 3 to Samba 4 at this stage, because there may be the features on
+which you may rely that are not present, or the mapping of
+your configuration and user database may not be complete.
+
+If you are upgrading, or looking to develop, test or deploy Samba4, you should
backup all configuration and data.
NEW FEATURES
We are aiming for Samba 4 to be powerful frontend to large
directories.
-CHANGES SINCE Alpha3
+CHANGES SINCE Alpha4
=====================
-In the time since Samba4 Alpha2 was released in December 2007, Samba has
+In the time since Samba4 Alpha4 was released in June 2008, Samba has
continued to evolve, but you may particularly notice these areas:
- Python Bindings: Bindings for Python are now used for all internal
- scripting, and the system python installation is used to run all
- Samba python scripts (in place of smbpython found in the previous
- alpha).
+ LDAP backend support restored (issues preventing the use of the LDAP
+ backend in alpha4 have been addressed).
+
+ SMB2 Support: The SMB2 server, while still disabled, has improved,
+ and now supports SMB2 signing.
+
+ OpenChange support: Updates have been made since alpha4 to better
+ support OpenChange's use of Samba4's libraries.
- As such Python is no longer optional, and configure will generate an
- error if it cannot locate an appropriate Python installation.
+ Faster ldb loading: A fix to avoid calling 'init_module' (which was
+ not defined by Samba modules, but was by the C library) will fix
+ some of the slowness in authentication.
SWAT Remains Disabled: Due to a lack of developer time and without a
long-term web developer to maintain it, the SWAT web UI remains been
GNU Make: To try and simplfy our build system, we rely on GNU Make
to avoid autogenerating a massive single makefile.
- Registry: Samba4's registry library has continued to improve.
-
- ID mapping: Samba4 uses the internal ID mapping in winbind for all
- but a few core users. Samba users should not appear in /etc/passwd,
- as Samba will generate new user and group IDs regradless.
-
- NTP: Samba4 can act as a signing server for the ntp.org NTP deamon,
- allowing NTPd to reply using Microsoft's non-standard signing
- scheme. A patch to make NTPd talk to Samba for this purpose has
- been submitted to the ntp.org project.
-
- CLDAP: Users should experience less arbitary delays and more success with
- group policy, domain joins and logons due to an improved
- implementation of CLDAP and the 'netlogon' mailslot datagrams.
-
- SMB2: The Samba4 SMB2 server and testsuite have been greatly
- improved, but the SMB2 server remains off by default.
-
- Secure DNS update: Configuration for GSS-TSIG updates of DNS records
- is now generated by the provision script.
These are just some of the highlights of the work done in the past few
months. More details can be found in our GIT history.
- There is no printing support in the current release.
-- There is no netbios browsing support in the current release
+- There is no NetBIOS browsing support in the current release
- The Samba4 port of the CTDB clustering support is not yet complete
- 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 is partly to assist with this problem).
+ and server. (The NTP work in the previous alpha is partly to assist
+ with this problem).
-- Samba4 alpha4 is currently only portable to recent Linux
+- Samba4 alpha5 is currently only portable to recent Linux
distributions. Work to return support for other Unix varients is
expected during the next alpha cycle
-- Samba4 alpha4 is incompatible with GnuTLS 2.0, found in Fedora 9 and
- recent Ubuntu releases. Please remove the
- gnutls-devel/libgnutls-dev package before compiling (otherwise 'make
- test' and LDAPS operations will hang).
+- Samba4 alpha5 is incompatible with GnuTLS 2.0, found in Fedora 9 and
+ recent Ubuntu releases. GnuTLS use may be disabled using the
+ --disable-gnutls argument to ./configure. (otherwise 'make test' and
+ LDAPS operations will hang).
RUNNING Samba4
==============
git.samba.org / kai / samba.git / blobdiff