-What's new in Samba 4 alpha16
+What's new in Samba 4 alpha19
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
WARNINGS
========
-Samba4 alpha16 is not a final Samba release, however we are now making
+Samba4 alpha19 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'.
-No migration path is currently provided between these two sets of
-technology. These missing migration paths will be the focus of
-development between now and a Samba 4.0 release.
While binaries for the stable file server are provided in this
release, for a stable, supported file server, Samba3 domain or AD
internal workings of the DC code is now implemented in python.
-CHANGES SINCE alpha15
+CHANGES SINCE alpha18
=====================
-For a list of changes since alpha 15, please see the git log.
+For a list of changes since alpha 18, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log release-4-0-0alpha15..release-4-0-0alpha16
+$ git log samba-4.0.0alpha18..samba-4.0.0alpha19
-The biggest user-visible change is that binaries from the Samba 3.x
-series of development are now built and installed. These binaries
-(smbd, nmbd, winbindd, net, testparm, etc) operate much as they do in
-the Samba 3.6 release candidates.
+Some major user-visible changes include:
-CHANGES
-=======
+CVE-2012-1182:
+ Samba 3.0.x to 3.6.3 are affected by a
+ vulnerability that allows remote code
+ execution as the "root" user.
-smb.conf changes
-----------------
+Portability to MacOS X. By using the CC_MD5*() routines we no longer
+segfault on MacOS X.
- Parameter Name Description Default
- -------------- ----------- -------
- announce version Removed
- announce as Removed
+The source4/librpc layer has been reworked to be much more robust to
+connection failures.
+
+security=share in smbd has now been removed.
+
+A segfault in vfs_aio_fork for the smbd file server has been fixed
+
+ldbadd and ldbmodify now handle each ldif file in a single
+transaction, when modifying a local ldb.
+
+Further improvements to the dlz_bind9 and internal DNS servers.
+
+
+Some major but less visible changes include:
+
+Initial support for s3fs, using the smbd file server in the AD Domain
+controller has been added (but not yet finished, so not exposed)
+
+Samba now only uses the _FILE_OFFSET_BITS=64 API for accessing large
+files, not the _LARGEFILE64_SOURCE API.
+
+All Samba daemons now monitor stdin when launched in the foreground,
+and shutdown when stdin is closed. We also ensure that all child
+processes are clened up by a similar mechanism. This ensures that
+stray processes do not hang around, particularly in make test.
+
+Further preparation work for moving to TDB2, a new version of Samba's core TDB
+database.
+
+Early implementation work on the SMB 2.2 protocol client and server as
+the team improves and develops support these new protocols.
+
+The last of the old-style krb5 ticket handling has been removed.
-Those familiar with Samba 3 can find a list of user-visible changes
-between the two technology sets provided in the NEWS file.
KNOWN ISSUES
============
+- upgradeprovision should not be run when upgrading to this release
+ from a recent release. No important database format changes have
+ been made since alpha16.
+
+- The BIND 9 DLZ plugin is compatible only with BIND 9.8, not BIND 9.9.
+
+- Systems with tdb or ldb installed as a system library may have
+ difficulty building this release of Samba4. The --disable-tdb2
+ configure switch may be of assistance.
+
+- Installation on systems without a system iconv (and developer
+ headers at compile time) is known to cause errors when dealing with
+ non-ASCII characters.
+
+- 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 in the 'samba' binary (use nmbd
- and 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
experience issues with DRS replication, as we have fixed many issues
here in response to feedback from our production users.
-- 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 Samba 4.0 as an AD DC
=============================
git.samba.org / abartlet / samba.git / .git / blobdiff