-What's new in Samba 4 alpha5
-============================
+What's new in Samba 4 alpha12
+=============================
Samba 4 is the ambitious next version of the Samba suite that is being
-developed in parallel to the stable 3.0 series. The main emphasis in
+developed in parallel to the stable 3.x series. The main emphasis in
this branch is support for the Active Directory logon protocols used
by Windows 2000 and above.
-Samba4 alpha5 follows on from the alpha release series we have been
+Samba4 alpha11 follows on from the alpha release series we have been
publishing since September 2007
WARNINGS
========
-Samba4 alpha5 is not a final Samba release. That is more a reference
+Samba4 alpha12 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
Samba4, you would find many things work, but that other key features
you may have relied on simply are not there yet.
-For example, while Samba 3.0 is an excellent member of a Active
+For example, while Samba 3 is an excellent member of a Active
Directory domain, Samba4 is happier as a domain controller, and it is
in this role where it has seen deployment into production.
We are aiming for Samba 4 to be powerful frontend to large
directories.
-CHANGES SINCE Alpha4
+CHANGES SINCE alpha11
=====================
-In the time since Samba4 Alpha4 was released in June 2008, Samba has
-continued to evolve, but you may particularly notice these areas:
+We have continued our commitment to provide a full DRS implementation for our
+AD implementation and therefore achieved also this time big steps forward.
- LDAP backend support restored (issues preventing the use of the LDAP
- backend in alpha4 have been addressed).
+Our progress on DRS is being tracked in the Samba wiki:
+http://wiki.samba.org/index.php/Samba4_DRS_TODO_List
- SMB2 Support: The SMB2 server, while still disabled, has improved,
- and now supports SMB2 signing.
+Beside this the release includes:
- OpenChange support: Updates have been made since alpha4 to better
- support OpenChange's use of Samba4's libraries.
+* a new build system based on WAF
+Andrew Tridgell (tridge) invested much time to bring this up. He achieved a
+marvellous work which brings us faster building, easier management and smaller
+binaries.
- 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.
+* enhancements in Samba4 winbind to provide a fairly good implementation of the
+most important functions needed by "libnss_winbind" and "pam_winbind"
+This two components allow a user/group mapping for Windows accounts on UNIX and
+UNIX-like systems. Therefore also these accounts can be used to connect to
+services as "ssh", "login", "Xsession" and so on.
+More informations available at http://wiki.samba.org/index.php/Samba4/Winbind
+and for winbind in general, "libnss_winbind" and "pam_winbind" in the Samba 3.X
+documentation.
- 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
- disabled (and would need to be rewritten in python in any case).
+* server side NT ACLs manipulation
+These can now also be set on the command line directly on the server. See
+"net acl" for further informations.
- GNU Make: To try and simplfy our build system, we rely on GNU Make
- to avoid autogenerating a massive single makefile.
+* dynamic DNS updates
+Up-to-date DNS entries are essential for Active Directory deployments. As for
+the moment Samba4 isn't yet capable to interoperate with Microsofts AD DNS
+server (regarding RPCs, ADs zone entries...) a kind of update script has been
+developed. It also permits the update of the "grant" and "resource" lists.
+* registry improvements
+The registry code was reworked, improved and retested. This was achieved by the
+new torture tests written by gd and some additional testing against Windows
+("regedit" - Windows Registry Editor and "regedt32" - Windows NT Registry Editor).
+Also some real bugs were fixed.
-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.
+* new Kerberos HEIMDAL release
+Andrew Bartlett (abartlet) imported a new release with various bugfixes
+* DCE/RPC code unification work
+Stefan Metzmacher (metze) started his work to unify these codebases between s3
+and s4
+
+* And much more
+We always try to fix bugs and keep improving the (source) quality of our
+program.
CHANGES
=======
- 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 alpha is partly to assist
+ and server. (The NTP work in the previous alphas are partly to assist
with this problem).
-- 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
+- The DRS replication code often fails, and is very new
-- 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).
+- Users upgrading existing databases to Samba4 should carefully
+ consult upgrading-samba4.txt. We have made a number of changes in
+ this release that should make it easier to upgrade in future.
+ Btw: there exists also a script under the "setup" directory of the
+ source distribution called "upgrade_from_s3" which should allow a step-up
+ from Samba3 to Samba4. It's not included yet in the binary distributions
+ since it's completely experimental!
RUNNING Samba4
==============
DEVELOPMENT and FEEDBACK
========================
+
+We need your help! Projects as Samba 4 live from the community feedback. If you
+provide expressive bug reports, some documentation snippets on the wiki or some
+real code patches - all is appreciated if it meets our quality criterias. Here
+you can find further references:
+
Bugs can be filed at https://bugzilla.samba.org/ but please be aware
that many features are simply not expected to work at this stage.
git.samba.org / ira / wip.git / blobdiff