-What's new in Samba 4 alpha3
-============================
+ =================================
+ Release Notes for Samba 3.5.0pre2
+ December 15, 2009
+ =================================
-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
-this branch is support for the Active Directory logon protocols used
-by Windows 2000 and above.
+This is the second preview release of Samba 3.5. 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/.
-Samba 4 is currently not yet in a state where it is usable in
-production environments. Note the WARNINGS below, and the STATUS file,
-which aims to document what should and should not work.
+Major enhancements in Samba 3.5.0 include:
-Samba4 alpha3 follows on from our first alpha release, made in
-September, and the Technology Preview series we have offered for some
-time now.
+General changes:
+o Add support for full Windows timestamp resolution
-WARNINGS
-========
+Protocol changes:
+o Experimental implementation of SMB2
-Samba4 alpha3 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.
+Printing Changes:
+o Add encryption support for connections to a CUPS server
-For example, while Samba 3.0 is an excellent member of a Active
-Directory domain, Samba4 is happier as a domain controller: (This is
-where we have done most of the research and development).
+Winbind changes:
+o Major refactoring
+o Asynchronous
-While Samba4 is subjected to an awesome battery of tests on an
-automated basis, and we have found Samba4 to be very stable in it's
-behaviour, we have to recommend against upgrading production servers
-from Samba 3 to Samba 4 at this stage. If you are upgrading an
-experimental server, or looking to develop and test Samba, you should
-backup all configuration and data.
-NEW FEATURES
-============
+General changes:
+================
-Samba4 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.
+Support for full Windows timestamp resolution has been added. This effectively
+makes us use Windows' full 100ns timestamp resolution if supported by the
+kernel (2.6.22 and higher) and the glibc (2.6 and higher).
-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.
+Protocol changes
+================
-The new VFS features in Samba 4 adapts the filesystem on the server to
-match the Windows client semantics, allowing Samba 4 to better match
-windows behaviour and application expectations. This includes file
-annotation information (in streams) and NT ACLs in particular. The
-VFS is backed with an extensive automated test suite.
+An EXPERIMENTAL implementation of the SMB2 protocol has been added. SMB2 can be
+enabled by setting "max protocol = smb2". SMB2 is a new implementation of the
+SMB protocol used by Windows Vista and higher.
-A new scripting interface has been added to Samba 4, allowing
-Python programs to interface to Samba's internals.
+Printing Changes
+================
-The Samba 4 architecture is based around an LDAP-like database that
-can use a range of modular backends. One of the backends supports
-standards compliant LDAP servers (including OpenLDAP), and we are
-working on modules to map between AD-like behaviours and this backend.
-We are aiming for Samba 4 to be powerful frontend to large
-directories.
+A new parameter "cups encrypt" has been added to control whether connections to
+CUPS servers will be encrypted or not. The default is to use unencrypted
+connections.
-CHANGES SINCE Alpha2
-=====================
+Winbind changes
+===============
-In the time since Samba4 Alpha2 was released in December 2007, Samba has
-continued to evolve, but you may particularly notice these areas:
+The Winbind daemon has been refactored internally to be asynchronous. The new
+Winbind will not be blocked by running 'wbinfo -g' or 'wbinfo -u'.
- Python Bindings: Bindings for Python are now in place, and used for
- Samba's provision script, slowly displacing EJS as the embedded
- scripting language
- SWAT Disabled: Due to a lack of developer time and without a
- long-term web developer to maintain it, the SWAT web UI has been
- disabled.
+######################################################################
+Changes
+#######
- Oplock support: Samba4's file server now supports oplocks
+smb.conf changes
+----------------
- GNU Make: To try and simplfy our build system, we rely on GNU Make
- to avoid autogenerating a massive single makefile.
+ Parameter Name Description Default
+ -------------- ----------- -------
-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.
+ create krb5 conf New yes
+ ctdb timeout New 0
+ cups encrypt New no
+ debug hires timestamp Changed Default yes
+ ldap deref New auto
+ ldap follow referral New auto
-CHANGES
-=======
+New configure options
+---------------------
-Those familiar with Samba 3 can find a list of user-visible changes
-since that release series in the NEWS file.
+--enable-external-libtdb Enable external tdb
+--enable-netapi Turn on netapi support
+--enable-pthreadpool Enable pthreads pool helper support
+--with-cifsumount Include umount.cifs (Linux only) support
+--with-codepagedir=DIR Where to put codepages
-KNOWN ISSUES
-============
-- Domain member support is in it's infancy, and is not comparable to
- the support found in Samba3.
+Commit Highlights
+=================
-- There is no printing support in the current release.
+o Björn Jacke <bj@sernet.de>
+ * Add support for full Windows timestamp resolution.
+ * Add encryption support for connections to a CUPS server.
-- The Samba4 port of the CTDB clustering support is not yet complete
-- Clock Synchronisation is critical. Many 'wrong password' errors are
- actually due to Kerberos objecting to a clock skew between client
- and server.
+o Volker Lendecke <vl@samba.org>
+ * Major internal refactoring of the Winbind daemon.
+ * Make Winbind asynchronous.
-RUNNING Samba4
-==============
+o Stefan Metzmacher <metze@samba.org>
+ * Implement the new SMB2 protocol (experimental).
-A short guide to setting up Samba 4 can be found in the howto.txt file
-in root of the tarball.
-DEVELOPMENT and FEEDBACK
-========================
-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.
+Changes since 3.5.0pre1
+-----------------------
-The Samba Wiki at http://wiki.samba.org should detail some of these
-development plans.
+o Michael Adam <obnox@samba.org>
+ * Fix the build when no external talloc and tdb are installed.
+ * Fix detection of CTDB headers on systems without system-libtalloc.
-Development and general discussion about Samba 4 happens mainly on
-the #samba-technical IRC channel (on irc.freenode.net) and
-the samba-technical mailing list (see http://lists.samba.org/ for
-details).
+
+o Jeremy Allison <jra@samba.org>
+ * BUG 6802: A created folder does not properly inherit permissions from
+ parent in vfs_acl_xattr.
+ * BUG 6837: "Too many open files" when trying to access large number of
+ files from Windows 7.
+ * BUG 6938 : No hook exists to check creation rights when using acl_xattr
+ module.
+ * Fix vfs_acl_xattr which was failing to call the NEXT connect function.
+ * Restructure the ACL code.
+ * Refactor reply_rmdir to use handle based code.
+
+
+o Dan Cox <dan@wep.net>
+ * BUG 2350: Add LDAP Alias Dereferencing support.
+
+
+o Günther Deschner <gd@samba.org>
+ * BUG 6929: Fix build with recent heimdal.
+ * Fix several printing issues.
+ * Fix the build on Mac OS X 10.6.2.
+ * Fix net and rpcclient after setprinterdataex changes.
+ * Add full support for level 8 printer drivers.
+ * Add more spoolss architectures to IDL.
+ * Fix enumprinter key client and server.
+ * Fix crash in EnumPrinterDataEx.
+
+
+o Björn Jacke <bj@sernet.de>
+ * Prefer posix_fallocate for doing "strict allocate".
+
+
+o Matt Kraai <mkraai@beckman.com>
+ * BUG 6860: Fix shared library build on QNX.
+
+
+o Volker Lendecke <vl@samba.org>
+ * BUG 6288: SWAT adds a second share when changing parameters of an existing
+ share.
+ * BUG 6435: Fix minor memory corruption.
+ * Restore "fake directory create times" as a share parameter.
+ * Fix explicit stat64 support.
+ * Add support for NetWkstaGetInfo 101 and 102.
+ * Add rpcclient wkssvc_enumerateusers.
+ * De-deprecate "write cache size" to prevent its removal without a proper
+ alternative.
+ * Allow more than 1000 users in BUILTIN\Users.
+
+
+o Jim McDonough <jmcd@samba.org>
+ * BUG 6967: Prevent glibc error on 'net ads join'.
+
+
+o Lars Müller <lars@samba.org>
+ * BUG 6710: Only install the cifs.upcall man page if CIFSUPCALL_PROGS was
+ set while configure.
+
+
+o Ian Puleston <ipuleston@sonicwall.com>
+ * Complete support for NetWkstaGetInfo/NetWkstaEnumUsers.
+
+
+o Karolin Seeger <kseeger@samba.org>
+ * Fix the build of the example VFS modules.
+
+
+o Bo Yang <boyang@samba.org>
+ * BUG 6879: Fix crash in Winbind.
+ * Fix crash in free_file_list().
+ * Give the user a chance to change password when password will expire soon.
+
+
+######################################################################
+Reporting bugs & Development Discussion
+#######################################
+
+Please discuss this release on the samba-technical mailing list or by
+joining the #samba-technical IRC channel on irc.freenode.net.
+
+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.5 product in the project's Bugzilla
+database (https://bugzilla.samba.org/).
+
+
+======================================================================
+== Our Code, Our Bugs, Our Responsibility.
+== The Samba Team
+======================================================================
git.samba.org / samba.git / blobdiff