-What's new in Samba 4 alpha20
+What's new in Samba 4 beta1
=============================
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.
-SECURITY RELEASE
-================
-
-This is a security release in order to address CVE-2012-2111
-(Incorrect permission checks when granting/removing privileges can
-compromise file server security).
-
-o CVE-2012-2111:
- Samba 3.4.x to 3.6.4 are affected by a
- vulnerability that allows arbitrary users
- to modify privileges on a file server.
-
-This is in regards to the smbd file server, which is shipped in Samba
-4.0 alpha. The AD DC is not directly impacted, as the LSA
-implementation differs.
WARNINGS
========
-Samba4 alpha20 is not a final Samba release, however we are now making
+Samba4 beta1 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
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. Existing installations will be
+unaffected at this stage.
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.
+
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 alpha19
+CHANGES SINCE alpha21
=====================
-For a list of changes since alpha 19, please see the git log.
+For a list of changes since alpha21, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log samba-4.0.0alpha19..samba-4.0.0alpha20
+$ git log samba-4.0.0alpha21..samba-4.0.0beta1
Some major user-visible changes include:
-Improvements to the 'samba-tool domain samba3upgrade' and
-samba_upgradedns tools
+The internal DNS server has had some stability improvements, and
+now handles forwarded DNS replies in an async manner.
-Stability improvements in the Samba4 winbind implementation (that
-used in the AD DC mode).
+The build of libtdb.so and libtalloc.so has been removed from the
+autoconf build. Use the build in lib/talloc and lib/tdb to build
+this software for use across the system.
-The BIND 9 DLZ plugin is now compatible with both BIND 9.8, and BIND 9.9.
+The smbclient and nmblookup binaries have been renamed in the top
+level build, so smbclient/nmblookup are now the implementations from
+the Samba 3.x heritage.
-dbcheck and runtime protection for the fSMORoleOwner attribute. This
-allows us to recover from a situation where the fSMORoleOwner is
-deleted.
+Improved handling of the cleanup of smbd child processes (removing a
+number of scary warnings from our log output).
-Support for storing the posixAccount and other auxiliary objectClass
-values (the values are not used by Samba as an AD DC at this stage,
-but may be used by clients).
+Much improved support for FreeBSD, including extended attribute
+support on the filesystem for the AD DC.
-Some major but less visible changes include:
-
-Continued early implementation work on the SMB 2.2 protocol client and server as
-the team improves and develops support these new protocols.
+KNOWN ISSUES
+============
-Initial work to build Samba using MIT kerberos in the top level waf
-build system. This is not complete at this time, but good progress is
-being made.
+- We are making this beta release to gain real-world use of the 's3fs'
+ file server combination we will use for the Samba 4.0 release.
+ Users should expect some rough edges: in particular, there are
+ warnings about invalid parameters from the two respective parameter
+ parsing engines.
+- 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 replicaton of
+ this partition is not yet reliable.
-KNOWN ISSUES
-============
+- 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
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 / nivanova / samba-autobuild / .git / blobdiff