-What's new in Samba 4 alpha18
+What's new in Samba 4.0 beta5
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
support for the Active Directory logon protocols used by Windows 2000
and above.
+
WARNINGS
========
-Samba4 alpha18 is not a final Samba release, however we are now making
+Samba 4.0 beta5 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'.
-
-While binaries for the stable file server are provided in this
-release, for a stable, supported file server, Samba3 domain or AD
-domain member installation, please run a Samba 3.x release, as we are
-still bedding down the new single build system.
+Be aware the this release contains the best of all of Samba's
+technology parts, both a file server (that you can reasonably expect
+to upgrade existing Samba 3.x releases to) and the AD domain
+controller work previously known as 'samba4'.
-Samba4 is subjected to an awesome battery of tests on an automated
+Samba 4.0 is subjected to an awesome battery of tests on an automated
basis, we have found Samba 4.0 to be very stable in it's behavior.
However, we still recommend against upgrading production servers from
-Samba 3.x release to Samba 4.0 alpha at this stage.
+Samba 3.x release to Samba 4.0 beta at this stage.
+
+In particular note that the new default configuration 's3fs' may have
+different stability characteristics compared with our previous default
+file server. We are making this release so that we can find and fix
+any of these issues that arise in the real world. New AD DC
+installations can provision or join with --use-ntvfs to obtain the
+previous default file server. See below how to continue using ntvfs
+in an existing installation.
If you are upgrading, or looking to develop, test or deploy Samba 4.0
-alpha releases, you should backup all configuration and data.
+beta releases, you should backup all configuration and data.
+
+
+UPGRADING
+=========
+
+Users upgrading from Samba 3.x domain controllers and wanting to use
+Samba 4.0 as an AD DC should use the 'samba-tool domain
+classicupgrade' command. See the wiki for more details:
+https://wiki.samba.org/index.php/Samba4/samba3upgrade/HOWTO
+
+Users upgrading from Samba 4.0 alpha and beta releases since alpha15
+should run 'samba-tool dbcheck --cross-ncs --fix'. Users upgrading
+from earlier alpha releases should contact the team for advice.
+
NEW FEATURES
============
-Samba 4.0 alpha supports the server-side of the Active Directory logon
+Samba 4.0 beta supports the server-side of the Active Directory logon
environment used by Windows 2000 and later, so we can do full domain
join and domain logon operations with these clients.
the infamous Kerberos PAC, and include it with the Kerberos tickets we
issue.
-Samba 4.0 alpha ships with two distinct file servers. The file server
-from the Samba 3.x series is 'smbd', and works with the binaries users
-would expect from that series (nmbd, winbindd, smbpasswd).
-
-Samba 4.0 also ships with a new file server, which is tuned to match
-the requirements of an AD domain controller. Users should not use the
-file server in the 'samba' binary for non-DC related tasks.
-
-A new scripting interface has been added to Samba 4, allowing Python
-programs to interface to Samba's internals, and many tools and
+Samba 4.0 beta ships with two distinct file servers. We now use the
+file server from the Samba 3.x series 'smbd' for all file serving by
+default. For pure file server work, the binaries users would expect
+from that series (nmbd, winbindd, smbpasswd) continue to be available.
+
+Samba 4.0 also ships with the 'NTVFS' file server. This file server
+is what was used in all previous alpha releases of Samba 4.0, and is
+tuned to match the requirements of an AD domain controller. We
+continue to support this, not only to provide continuity to
+installations that have deployed it as part of an AD DC, but also as a
+running example of the NT-FSA architecture we expect to move smbd to in
+the longer term.
+
+As mentioned above, this change to the default file server may cause
+instability, as we learn about the real-world interactions between
+these two key components.
+
+As DNS is an integral part of Active Directory, we also provide a DNS
+solution, using the BIND DLZ mechanism in versions 9.8 and 9.9.
+During the provision, a configuration file will be generated for bind
+to make it use this plugin. We also have a project to provide a
+minimal internal DNS server from within the Samba process, for easier
+'out of the box' configuration. Note however that this is not yet
+complete (pending addition of secure DNS update support).
+
+To provide accurate timestamps to Windows clients, we integrate with
+the NTP project to provide secured NTP replies.
+
+Finally, a new scripting interface has been added to Samba 4, allowing
+Python programs to interface to Samba's internals, and many tools and
internal workings of the DC code is now implemented in python.
-CHANGES SINCE alpha17
+CHANGES SINCE beta4
=====================
-For a list of changes since alpha 17, please see the git log.
+For a list of changes since beta4, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log samba-4.0.0alpha17..samba-4.0.0alpha18
+$ git log samba-4.0.0beta4..samba-4.0.0beta5
Some major user-visible changes include:
-Improvements to DNS servers. Samba4 now has 3 options for the
-handling of DNS: The default option is to use the BIND 9.8 DLZ plugin,
-which stores the information about the DNS zone in the directory.
-There is also an internal DNS server (but which does not support
-secure DNS updates at this time) and the flat file BIND 9.8 backend
-(storing the data in traditional zone files).
+- The issue with beta4 being unable to build with a released version of
+ ldb has been resolved.
+
+- The two parameter tables for our two smb.conf parsing engines have
+ been merged. This removes the ugly (but harmless) "unknown
+ parameter xxx" warnings, particularly from the smbd child process.
+
+- Major issues have been fixed in conflict and missing/deleted parent
+ handling in or DRS replication engine.
-To migrate from zone files to directory based DNS servers, a migration
-tool (upgradedns) has been added.
+- Safety improvements to prevent corruption of read-write replicas
+ by manual replication from a read-only replica.
-samba-tool dns commands to manage DNS records stored in directory.
+- Improvements to dbcheck to correct incorrect instanceType values from
+ the above and to relocate objects with missing parents.
-smbwrapper (a user-space file system based on LD_PRELOAD) has been
-removed.
+- smbd no longer places all accounts in the 'Domain Users' of the AD
+ domain to which it is joined
-Improvement to the upgrade process between Samba 3.x domains and Samba
-4.0 AD domains (samba-tool domain samba3upgrade).
+- AES support in NETLOGON Schannel
-Some major but less visible changes include:
+- DCE/RPC timeout handling no longer crashes
-Major work to bridge the code gap between the major parts of the code
-base, including a common loadparm wrapper, smb client library, as well
-as NTLMSSP, GSSAPI and SPNEGO code as part of the GENSEC
-authentication and authorization stack.
+- "socket address" is now "nbt client socket address" as it only
+ controls the binding of the NetBIOS client, not other protocols.
+ See 'bind interfaces only = yes'. This parameter is also now depricated.
-Preparation work for moving to TDB2, a new version of Samba's core TDB
-database.
+- nmbd now always binds to it's broadcast sockets explicitly, rather
+ than just relying on the socket address above.
-smbtorture tests for SMB 2 and SMB 2.2 as the team improves and
-develops support these new protocols.
+Less visible, but important changes under the hood include:
-Major cleanup and removal of global variables in the smbd SMB and SMB2 server.
+- Continued work to support SMB2 and SMB3
-Heimdal security issue 2012-01-11 - libkrb5 checksum - denial of serice
-http://www.h5l.org//advisories.html?show=2012-01-11
+- Continued work to use async IO to improve file server performance.
+
+- Patches to ensure that talloc_tos() and talloc_stackframe() are
+ always used correctly.
KNOWN ISSUES
============
+- This release makes the s3fs file server the default, as this is the
+ file server combination we will use for the Samba 4.0 release.
+
+- Modifying of group policies by members of the Domain Administrators
+ group is not possible with the s3fs file server, only with the ntvfs
+ file server. This is due to the underlying POSIX ACL not being set
+ at provision time.
+
+- For similar reasons, sites with ACLs stored by the ntvfs file server
+ may wish to continue to use that file server implementation, as a
+ posix ACL will similarly not be set in this case.
+
+- Replication of DNS data from one AD server to another may not work.
+ The DNS data used by the internal DNS server and bind9_dlz is stored
+ in an application partition in our directory. The replication of
+ this partition is not yet reliable.
+
+- Replication may fail on FreeBSD due to getaddrinfo() rejecting names
+ containing _. A workaround will be in the next beta.
+
- 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. (Distributors who (rightly)
- have difficulty with this may wish to wait until a future release,
- which will soon fix this issue).
-
- 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
server.
-- There is no printing support in the 'samba' binary (use smbd instead)
-
- There is no NetBIOS browsing support (network neighbourhood) in the
'samba' binary (use nmbd and smbd instead)
experience issues with DRS replication, as we have fixed many issues
here in response to feedback from our production users.
+
RUNNING Samba 4.0 as an AD DC
=============================
git.samba.org / samba.git / blobdiff