- =================================
- Release Notes for Samba 3.6.0pre1
- July 28, 2010
- =================================
+What's new in Samba 4 alpha21
+=============================
+Samba 4.0 will be the next version of the Samba suite and incorporates
+all the technology found in both the Samba4 alpha series and the
+stable 3.x series. The primary additional features over Samba 3.6 are
+support for the Active Directory logon protocols used by Windows 2000
+and above.
-This is the first preview release of Samba 3.6. This is *not*
-intended for production environments and is designed for testing
-purposes only. Please report any defects via the Samba bug reporting
-system at https://bugzilla.samba.org/.
+WARNINGS
+========
-Major enhancements in Samba 3.6.0 include:
+Samba4 alpha21 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 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.
-Changed security defaults
--------------------------
+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 with --use-ntvfs to obtain the previous default file
+server. Existing installations will be unaffected at this stage.
-Samba 3.6 has adopted a number of improved security defaults that will
-impact on existing users of Samba.
+If you are upgrading, or looking to develop, test or deploy Samba 4.0
+alpha releases, you should backup all configuration and data.
- client ntlmv2 auth = yes
- client use spnego principal = no
- send spnego principal = no
+NEW FEATURES
+============
-The impact of 'client ntlmv2 auth = yes' is that by default we will not
-use NTLM authentication as a client. This applies to the Samba client
-tools such as smbclient and winbind, but does not change the separately
-released in-kernel CIFS client. To re-enable the poorer NTLM encryption
-set '--option=clientusentlmv2auth=no' on your smbclient command line, or
-set 'client ntlmv2 auth = no' in your smb.conf
+Samba 4.0 alpha 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 impact of 'client use spnego principal = no' is that we may be able
-to use Kerberos to communicate with a server less often in smbclient,
-winbind and other Samba client tools. We may fall back to NTLMSSP in
-more situations where we would previously rely on the insecure
-indication from the 'NegProt' CIFS packet. This mostly occursed when
-connecting to a name alias not recorded as a servicePrincipalName for
-the server. This indication is not available from Windows 2008 or later
-in any case, and is not used by modern Windows clients, so this makes
-Samba's behaviour consistent with other clients and against all servers.
+Our Domain Controller (DC) implementation includes our own built-in
+LDAP server and Kerberos Key Distribution Center (KDC) as well as the
+Samba3-like logon services provided over CIFS. We correctly generate
+the infamous Kerberos PAC, and include it with the Kerberos tickets we
+issue.
-The impact of 'send spnego principal = no' is to match Windows 2008 and
-not to send this principal, making existing clients give more consistent
-behaviour (more likely to fall back to NTLMSSP) between Samba and
-Windows 2008, and between Windows versions that did and no longer use
-this insecure hint.
+Samba 4.0 alpha 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.
-SMB2 support
-------------
+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.
-SMB2 support in 3.6.0 is fully functional (with one omission),
-and can be enabled by setting:
+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.
-max protocol = SMB2
-in the [global] section of your smb.conf and re-starting
-Samba. All features should work over SMB2 except the modification
-of user quotas using the Windows quota management tools.
-As this is the first release containing what we consider
-to be a fully featured SMB2 protocol, we are not enabling
-this by default, but encourage users to enable SMB2 and
-test it. Once we have enough confirmation from Samba
-users and OEMs that SMB2 support is stable in wide user
-testing we will enable SMB2 by default in a future Samba
-release.
+CHANGES SINCE alpha20
+=====================
+For a list of changes since alpha20, please see the git log.
-Internal Winbind passdb changes
--------------------------------
+$ git clone git://git.samba.org/samba.git
+$ cd samba.git
+$ git log samba-4.0.0alpha20..samba-4.0.0alpha21
-Winbind has been changed to use the internal samr and lsa rpc pipe to get
-local user and group information instead of calling passdb functions. The
-reason is to use more of our infrastructure and test this infrastructure by
-using it. With this approach more code in Winbind is shared.
+Some major user-visible changes include:
+For installations that do not need an AD Domain controller, we can now
+build using MIT Kerberos from the local system. This is important for
+some distributors. This is enabled with the new --with-system-mitkrb5
+configure option. A synonym is the new --without-ad-dc option.
-New Spoolss code
-----------------
+The 's3fs' effort has moved to a new stage, with this now being the
+default mode of operation for new provisions.
-The spoolss and the old RAP printing code have been completely
-overhauled and refactored.
+The BIND 9 DLZ plugin has had some stability improvements under BIND reloads.
-All calls from lanman/printing code has been changed to go through the
-spoolss RPC interfaces, this allows us to keep all checks in one place
-and avoid special cases in the main printing code.
-Printing code has been therefore confined within the spoolss code.
+The 'samba-tool domain samba3upgrade' tool will now generally import
+all group members, and correctly imports domain password policies.
-All the printing code, including the spoolss RPC interfaces has been
-changed to use the winreg RPC interfaces to store all data.
-All data has been migrated from custom, arbitrary TDB files to the
-registry interface. This transition allow us to present correct data to
-windows client accessing the server registry through the winreg RPC
-interfaces to query for printer data. Data is served out from a real
-registry implementation and therefore arguably 100% forward compatible.
+Some major but less visible changes include:
-Migration code from the previous TDB files formats is provided. This
-code is automatically invoked the first time the new code is run on the
-server. Although manual migration is also available using the 'net
-printer migrate' command.
+Continued early implementation work on the SMB 2.2 protocol client and server as
+the team improves and develops support these new protocols.
-These changes not only make all the spoolss code much more closer to
-"the spec", it also greatly improves our internal testing of both
-spoolss and winreg interfaces, and reduces overall code duplication.
-As part of this work, new tests have been also added to increase
-coverage.
+KNOWN ISSUES
+============
-This code will also allow, in future, an easy transition to split out
-the spooling functions into a separate daemon for those OEMs that do not
-need printing functionality in their appliances, reducing the code
-footprint.
+- We are making this alpha 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.
+- There have been improvements to FreeBSD support, but more work is
+ still required to finish this effort
-SMB Traffic Analyzer
---------------------
+- upgradeprovision should not be run when upgrading to this release
+ from a recent release. No important database format changes have
+ been made since alpha16.
-Added the new SMB Traffic Analyzer (SMBTA) VFS module protocol 2
-featuring encryption, multiple arguments, and easier parseability. A new
-tool 'smbta-util' has been created to control the encryption behaviour
-of SMBTA. For compatibility, SMBTA by default operates on version 1.
-There are programs consuming the data that the module sends.
+- Installation on systems without a system iconv (and developer
+ headers at compile time) is known to cause errors when dealing with
+ non-ASCII characters.
-More information can be found on
-http://holger123.wordpress.com/smb-traffic-analyzer/
+- 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 NetBIOS browsing support (network neighbourhood) in the
+ 'samba' binary (use nmbd and smbd instead)
-######################################################################
-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 alphas are partly to assist
+ with this problem).
-smb.conf changes
-----------------
+- The DRS replication code may fail. Please contact the team if you
+ experience issues with DRS replication, as we have fixed many issues
+ here in response to feedback from our production users.
- Parameter Name Description Default
- -------------- ----------- -------
+RUNNING Samba 4.0 as an AD DC
+=============================
- log writeable files on exit New No
- ctdb locktime warn threshold New 0
- smb2 max read New 1048576
- smb2 max write New 1048576
- smb2 max trans New 1048576
- username map cache time New 0
- async smb echo handler New No
+A short guide to setting up Samba 4 as an AD DC can be found on the wiki:
+ http://wiki.samba.org/index.php/Samba4/HOWTO
-######################################################################
+#######################################
Reporting bugs & Development Discussion
#######################################
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
-be filed under the Samba 3.6 product in the project's Bugzilla
+be filed under the Samba 4.0 product in the project's Bugzilla
database (https://bugzilla.samba.org/).
git.samba.org / obnox / samba / samba-obnox.git / blobdiff