-What's new in Samba 4 alpha6
-============================
+What's new in Samba 4 alpha13
+=============================
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 alpha6 follows on from the alpha release series we have been
-publishing since September 2007
+Samba4 alpha13 follows on from the alpha release series we have been
+publishing since September 2007. Since this file has referred to alpha 12
+for a while before any release happened and since Debian packages
+have been published that presumed the existance of a alpha12 release
+we are skipping alpha12 and going straight to alpha13.
WARNINGS
========
-Samba4 alpha6 is not a final Samba release. That is more a reference
+Samba4 alpha13 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.
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.
+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.
We are aiming for Samba 4 to be powerful frontend to large
directories.
-CHANGES SINCE Alpha5
+CHANGES SINCE alpha11
=====================
-In the time since Samba4 Alpha5 was released in June 2008, Samba has
-continued to evolve, but you may particularly notice these areas
-(in no particular order):
+We have continued our commitment to provide a full DRS implementation for our
+AD implementation and therefore achieved also this time big steps forward.
- The source code for various libraries that are used by both Samba 3 and
- Samba 4 are now shared between the two rather than duplicated
- (and being slightly diverged).
+Our progress on DRS is being tracked in the Samba wiki:
+http://wiki.samba.org/index.php/Samba4_DRS_TODO_List
- The tevent library has been split out and is now usable on its own.
+Beside this the release includes (among a lot of other things):
- Several crash bugs and memory leaks in the registry library have been fixed.
+* 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.
- The Python modules have been extended and are no longer generated using SWIG.
+* 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.
- Stream renames are now supported.
+* 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.
- The provision script now has an interactive mode.
+* 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.
- The (broken) copy of CTDB has been removed.
+* 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.
- More work towards supporting an OpenLDAP backend.
+* new Kerberos HEIMDAL release
+Andrew Bartlett (abartlet) imported a new release with various bugfixes
- Initial work on using the Microsoft LDAP schema.
-
- The storage of schemas in LDB is now much more efficient.
-
- Support for extended DNs in LDB has been added.
-
- Incoming trusts are now supported.
-
- Compatibility of the registry server with several Windows versions has been
- improved.
-
- Improvements to LSA.idl for better functionality in the usrmgr.exe.
-
- Improved handling of non-standard characters in passwords.
-
- The embedded JavaScript library has been removed in favor of Python.
-
- The WMI implementation has been re-added, but does not completely work yet.
-
- xpress compression is now supported in the NDR layer.
-
- The main binary is now named "samba" rather than "smbd".
-
- A simple script for setting the expiration of a user was added.
-
- It is now possible to use the system-installed Heimdal using the
- experimental --enable-external-heimdal option to configure.
-
- The LDB library is now completely asynchronous internally.
-
- Various unknowns and correctness issues in the drsblobs and drsuapi RPC
- interface implementations have been fixed.
-
- It is now possible to connect to an LDAP backend using SASL credentials.
-
- Multi-fragment NTtrans request support has been added.
-
- The DCE/RPC server can now listen on a separate pipe to allow DCE/RPC
- connections forwarded from Samba 3. The user credentials are provided
- by the client.
-
- A large number of bugs in the SMB2 implementation have been fixed.
-
- Auxiliary classes in LDAP schema conversion are now collapsed.
-
-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.
+* 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 alpha6 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 alpha6 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.
+that many features are simply not expected to work at this stage.
The Samba Wiki at http://wiki.samba.org should detail some of these
development plans.
git.samba.org / sfrench / samba-autobuild / .git / blobdiff