-What's new in Samba 4.0 beta6
+What's new in Samba 4.0 beta8
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
WARNINGS
========
-Samba 4.0 beta6 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
+Samba 4.0 beta8 is not a final Samba release, however we are now making
+good progress towards a Samba 4.0 release. However, this is expected to be the
+last beta release before we start on our release candidate series.
+
+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'.
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 behaviour.
-However, we still recommend against upgrading production servers from
-Samba 3.x release to Samba 4.0 beta at this stage.
+However, as with all our pre-releases we still recommend against
+upgrading production servers from Samba 3.x release to Samba 4.0 beta
+at this stage.
If you are upgrading, or looking to develop, test or deploy Samba 4.0
beta releases, you should backup all configuration and data.
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.
+Users upgrading from Samba 4.0 alpha and beta releases since alpha15
+should run 'samba-tool dbcheck --cross-ncs --fix' before re-starting
+Samba. Users upgrading from earlier alpha releases should contact the
+team for advice.
+
+Users upgrading an AD DC from any previous release should run
+'samba-tool ntacl sysvolreset' to re-sync ACLs on the sysvol share
+with those matching the GPOs in LDAP and the defaults from an initial
+provision. This will set an underlying POSIX ACL if required (eg not
+using the NTVFS file server).
+If you used the BIND9_FLATFILE or BIND9_DLZ features,
+you'll have to add '-dns' to the 'server services' option,
+as the internal dns server (SAMBA_INTERNAL) is the default now.
NEW FEATURES
============
For pure file server work, the binaries users would expect from that
series (nmbd, winbindd, smbpasswd) continue to be available. When
running an AD DC, you only need to run 'samba' (not
-nmbd/smbd/winbind), as the required services are co-ordinated by this
+nmbd/smbd/winbind), as the required services are co-coordinated by this
master binary.
-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).
+As DNS is an integral part of Active Directory, we also provide two DNS
+solutions, a simple internal DNS server for 'out of the box' configurations
+and a more elaborate BIND plugin using the BIND DLZ mechanism in versions
+9.8 and 9.9. During the provision, you can select which backend to use.
+With the internal backend, your DNS server is good to go.
+If you chose the BIND_DLZ backend, a configuration file will be generated
+for bind to make it use this plugin, as well as a file explaining how to
+set up bind.
To provide accurate timestamps to Windows clients, we integrate with
the NTP project to provide secured NTP replies. To use you need to
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 beta5
+CHANGES SINCE beta8
+===================
+
+The smbd file server now offers SMB3 as the maximum protocol
+by default. Samba can negotiate version 3 of the SMB protocol
+and supports the required features, including all required
+features of SMB 2.1 and SMB 2.0. Note that this does not imply
+that Samba implements all features of SMB3 since many of them
+are optional capabilities. Examples of features that Samba does
+not implement yet are leases (SMB 2.1) and multi-channel (SMB 3).
+
+Samba now offers an initial support for SMB2 durable file handles.
+These are enabled by default and can be turned off on a per share
+basis by setting "durable handles = no" on the share configuration.
+Note that in order to prevent conflicts with other applications
+accessing the same files, durable handles are only granted on
+shares that are configured for CIFS/SMB2-only access, i.e. more
+explicitly shares that are configured for minimal interoperability
+with these settings:
+
+ kernel oplocks = no
+ kernel share modes = no
+ posix locking = no
+
+The option "kernel share modes" has been introduced to be able
+to turn the translation of SMB share modes into kernel flocks
+off.
+
+The 'provision' script was merged into 'samba-tool'
+as 'samba-tool domain provision' the arguments are still
+the same.
+
+The 'updateprovision' script was renamed to 'samba_upgradeprovision'.
+
+We changed the default dns implementation to the internal dns server
+(SAMBA_INTERNAL). BIND9_FLATFILE and BIND9_DLZ are still available,
+but you'll have to add '-dns' to the 'server services' option
+to disable the internal dns server.
+The default for 'allow dns updates' has changed to 'secure only'.
+
+CHANGES SINCE beta7
=====================
-For a list of changes since beta5, please see the git log.
+For a list of changes since beta7, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log samba-4.0.0beta5..samba-4.0.0beta6
+$ git log samba-4.0.0beta7..samba-4.0.0beta8
Some major user-visible changes include:
-- Provision is now faster, as we now correctly use the database
- indices during the provision
-
-- Support for handling of Extended Signatures (Session Key Protection)
+- A fix for a segfault/abort on startup of the 'samba' binary in the
+ credentials_secrets code.
-- A (unverified at this time) fix for expanding memory use in our
- AD DRS replication server.
+- A fix for samba-tool classicupgrade of pdb_ldap-based domains
-- A fix for supporting the userWorkstations restriction in the KDC
+- A fix for samba-tool domain exportkeyab only exporting DES keys
-- Support for upgrading classic domains that may not have all the
- default domain policies set.
+- Printing is now enabled on the AD DC
-Less visible, but important changes under the hood include:
+- Fix bug #9124 - Samba fails to set "inherited" bit on inherited ACE's.
-- Continued work to support SMB2 and SMB3
+- We now avoid printing secret attributes (such as unicodePwd and
+ suppliementalCredentials) in ldb trace logs
-- Continued work to use async IO to improve file server performance.
+- s3-printing: fix bug 9123 lprng job tracking errors
-- Patches to ensure that talloc_tos() and talloc_stackframe() are
- always used correctly.
-
-- Preparation for correctly setting POSIX ACLs during provision.
+- A fix for building with MIT Kerberos
KNOWN ISSUES
============
+- 'samba-tool domain classicupgrade' will fail when setting ACLs on
+ the GPO folders with NT_STATUS_INVALID_ONWER in the default
+ configuration. This happens if, as is typical a 'domain admins'
+ group (-512) is mapped in the passdb backend being upgraded. This
+ is because the group mapping to a GID only prevents Samba from
+ allocating a uid for that group. The uid is needed so the 'domain
+ admins' group can own the GPO file objects.
+
+ To work around this issue, remove the 'domain admins' group before
+ upgrade, as it will be re-created automatically. You will
+ of course need to fill in the group membership again. A future release
+ will make this automatic, or find some other workaround.
+
- 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. Recursivly giving 'domain administrators' write
- access to the contents of the sysvol share using a windows client
- will fix this in the interim.
-
- 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.
this partition is not yet reliable.
- Replication may fail on FreeBSD due to getaddrinfo() rejecting names
- containing _. A workaround will be in a future next beta.
+ containing _. A workaround will be in a future beta.
- upgradeprovision should not be run when upgrading to this release
from a recent release. No important database format changes have
git.samba.org / obnox / samba / samba-obnox.git / blobdiff