Release Announcements
=====================
-This is the first preview release of Samba 4.9. This is *not*
+This is the first preview release of Samba 4.11. 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.9 will be the next version of the Samba suite.
+Samba 4.11 will be the next version of the Samba suite.
UPGRADING
=========
+SMB1 is disabled by default
+---------------------------
-NEW FEATURES/CHANGES
-====================
+The defaults of 'client min protocol' and 'server min protocol'
+have been changed to SMB2_02.
+This means clients without support for SMB2 or SMB3 are no longer
+able to connect to smbd (by default).
-net ads setspn
----------------
+It also means client tools like smbclient and other,
+as well as applications making use of libsmbclient are no longer
+able to connect to servers without SMB2 or SMB3 support (by default).
-There is a new 'net ads setspn' sub command for managing Windows SPN(s)
-on the AD. This command aims to give the basic functionality that is
-provided on windows by 'setspn.exe' e.g. ability to add, delete and list
-Windows SPN(s) stored in a Windows AD Computer object.
+It's still possible to allow SMB1 dialects, e.g. NT1, LANMAN2
+and LANMAN1 for client and server, as well as CORE and COREPLUS on
+the client.
-The format of the command is:
+Note that most commandline tools e.g. smbclient, smbcacls and others
+also support the --option argument to overwrite smb.conf options,
+e.g. --option='client min protocol=NT1' might be useful.
-net ads setspn list [machine]
-net ads setspn [add | delete ] SPN [machine]
+As Microsoft no longer installs SMB1 support in recent releases
+or uninstalls it after 30 days without usage, the Samba Team
+tries to get remove the SMB1 usage as much as possible.
-'machine' is the name of the computer account on the AD that is to be managed.
-If 'machine' is not specified the name of the 'client' running the command
-is used instead.
+SMB1 is officially deprecated and might be removed step by step
+in the following years. If you have a strong requirement for SMB1
+(except for supporting old Linux Kernels), please file a bug
+at https://bugzilla.samba.org and let us know about the details.
-The format of a Windows SPN is
- 'serviceclass/host:port/servicename' (servicename and port are optional)
+NEW FEATURES/CHANGES
+====================
-serviceclass/host is generally sufficient to specify a host based service.
+Default samba process model
+---------------------------
-net ads keytab changes
-----------------------
-net ads keytab add no longer attempts to convert the passed serviceclass
-(e.g. nfs, html etc.) into a Windows SPN which is added to the Windows AD
-computer object. By default just the keytab file is modified.
+The default for the --model argument passed to the samba executable has changed
+from 'standard' to 'prefork'. This means a difference in the number of samba
+child processes that are created to handle client connections. The previous
+default would create a separate process for every LDAP or NETLOGON client
+connection. For a network with a lot of persistent client connections, this
+could result in significant memory overhead. Now, with the new default of
+'prefork', the LDAP, NETLOGON, and KDC services will create a fixed number of
+worker processes at startup and share the client connections amongst these
+workers. The number of worker processes can be configured by the 'prefork
+children' setting in the smb.conf (the default is 4).
-A new keytab subcommand 'add_update_ads' has been added to preserve the
-legacy behaviour. However the new 'net ads setspn add' subcommand should
-really be used instead.
+Authentication Logging.
+-----------------------
-net ads keytab create no longer tries to generate SPN(s) from existing
-entries in a keytab file. If it is required to add Windows SPN(s) then
-'net ads setspn add' should be used instead.
+Winbind now logs PAM_AUTH and NTLM_AUTH events, a new attribute "logonId" has
+been added to the Authentication JSON log messages. This contains a random
+logon id that is generated for each PAM_AUTH and NTLM_AUTH request and is passed
+to SamLogon, linking the windbind and SamLogon requests.
-Local authorization plugin for MIT Kerberos
--------------------------------------------
+The serviceDescription of the messages is set to "winbind", the authDescription
+is set to one of:
+ "PASSDB, <command>, <pid>"
+ "PAM_AUTH, <command>, <pid>"
+ "NTLM_AUTH, <command>, <pid>"
+where:
+ <command> is the name of the command makinmg the winbind request i.e. wbinfo
+ <pid> is the process id of the requesting process.
-This plugin controls the relationship between Kerberos principals and AD
-accounts through winbind. The module receives the Kerberos principal and the
-local account name as inputs and can then check if they match. This can resolve
-issues with canonicalized names returned by Kerberos within AD. If the user
-tries to log in as 'alice', but the samAccountName is set to ALICE (uppercase),
-Kerberos would return ALICE as the username. Kerberos would not be able to map
-'alice' to 'ALICE' in this case and auth would fail. With this plugin account
-names can be correctly mapped. This only applies to GSSAPI authentication,
-not for the getting the initial ticket granting ticket.
+The version of the JSON Authentication messages has been changed to 1.2 from 1.1
-VFS audit modules
------------------
+LDAP referrals
+--------------
-The vfs_full_audit module has changed it's default set of monitored successful
-and failed operations from "all" to "none". That helps to prevent potential
-denial of service caused by simple addition of the module to the VFS objects.
+The scheme of returned LDAP referrals now reflects the scheme of the original
+request, i.e. referrals received via ldap are prefixed with "ldap://"
+and those over ldaps are prefixed with "ldaps://"
-Also, modules vfs_audit, vfs_ext_audit and vfs_full_audit now accept any valid
-syslog(3) facility, in accordance with the manual page.
+Previously all referrals were prefixed with "ldap://"
-Database audit support
-----------------------
+Bind9 logging
+-------------
-Changes to the Samba AD's sam.ldb database are now logged to Samba's debug log
-under the "dsdb_audit" debug class and "dsdb_json_audit" for JSON formatted log
-entries.
+It is now possible to log the duration of DNS operations performed by Bind9
+This should aid future diagnosis of performance issues, and could be used to
+monitor DNS performance. The logging is enabled by setting log level to
+"dns:10" in smb.conf
-Transaction commits and roll backs are now logged to Samba's debug logs under
-the "dsdb_transaction_audit" debug class and "dsdb_transaction_json_audit" for
-JSON formatted log entries.
+The logs are currently Human readable text only, i.e. no JSON formatted output.
-Password change audit support
------------------------------
+Log lines are of the form:
-Password changes in the AD DC are now logged to Samba's debug logs under the
-"dsdb_password_audit" debug class and "dsdb_password_json_audit" for JSON
-formatted log entries.
+ <function>: DNS timing: result: [<result>] duration: (<duration>)
+ zone: [<zone>] name: [<name>] data: [<data>]
-Group membership change audit support
--------------------------------------
+ durations are in microseconds.
-Group membership changes on the AD DC are now logged to
-Samba's debug log under the "dsdb_group_audit" debug class and
-"dsdb_group_json_audit" for JSON formatted log entries.
+Default schema updated to 2012_R2
+---------------------------------
-Log Authentication duration
----------------------------
+Default AD schema changed from 2008_R2 to 2012_R2. 2012_R2 functional level
+is not yet available. Older schemas can be used by provisioning with the
+'--base-schema' argument. Existing installations can be updated with the
+samba-tool command "domain schemaupgrade".
-For NTLM and Kerberos KDC authentication, the authentication duration is now
-logged. Note that the duration is only included in the JSON formatted log
-entries.
+Samba's replication code has also been improved to handle replication
+with the 2012 schema (the core of this replication fix has also been
+backported to 4.9.11 and will be in a 4.10.x release).
-JSON library Jansson required for the AD DC
--------------------------------------------
+GnuTLS 3.2 required
+-------------------
-By default the Jansson JSON library is required for Samba to build.
-It is strictly required for the Samba AD DC, and is optional for
-builds --without-ad-dc by specifying --without-json-audit at configure
-time.
+Samba is making efforts to remove in-tree cryptographic functionality,
+and to instead rely on externally maintained libraries. To this end,
+Samba has chosen GnuTLS as our standard cryptographic provider.
-New Experimental LMDB LDB backend
----------------------------------
+Samba now requires GnuTLS 3.2 to be installed (including development
+headers at build time) for all configurations, not just the Samba AD
+DC.
-A new experimental LDB backend using LMDB is now available. This allows
-databases larger than 4Gb (Currently the limit is set to 6Gb, but this will be
-increased in a future release). To enable lmdb, provision or join a domain using
-the --backend-store=mdb option.
-
-This requires that a version of lmdb greater than 0.9.16 is installed and that
-samba has not been built with the --without-ldb-lmdb option.
-
-Please note this is an experimental feature and is not recommended for
-production deployments.
-
-Password Settings Objects
--------------------------
-Support has been added for Password Settings Objects (PSOs). This AD feature is
-also known as Fine-Grained Password Policies (FGPP).
-
-PSOs allow AD administrators to override the domain password policy settings
-for specific users, or groups of users. For example, PSOs can force certain
-users to have longer password lengths, or relax the complexity constraints for
-other users, and so on. PSOs can be applied to groups or to individual users.
-When multiple PSOs apply to the same user, essentially the PSO with the best
-precedence takes effect.
-
-PSOs can be configured and applied to users/groups using the 'samba-tool domain
-passwordsettings pso' set of commands.
-
-Domain backup and restore
--------------------------
-A new samba-tool command has been added that allows administrators to create a
-backup-file of their domain DB. In the event of a catastrophic failure of the
-domain, this backup-file can be used to restore Samba services.
-
-The new 'samba-tool domain backup online' command takes a snapshot of the
-domain DB from a given DC. In the event of a catastrophic DB failure, all DCs
-in the domain should be taken offline, and the backup-file can then be used to
-recreate a fresh new DC, using the 'samba-tool domain backup restore' command.
-Once the backed-up domain DB has been restored on the new DC, other DCs can
-then subsequently be joined to the new DC, in order to repopulate the Samba
-network.
-
-Domain rename tool
-------------------
-Basic support has been added for renaming a Samba domain. The rename feature is
-designed for the following cases:
-1). Running a temporary alternate domain, in the event of a catastrophic
-failure of the regular domain. Using a completely different domain name and
-realm means that the original domain and the renamed domain can both run at the
-same time, without interfering with each other. This is an advantage over
-creating a regular 'online' backup - it means the renamed/alternate domain can
-provide core Samba network services, while trouble-shooting the fault on the
-original domain can be done in parallel.
-2). Creating a realistic lab domain or pre-production domain for testing.
-
-Note that the renamed tool is currently not intended to support a long-term
-rename of the production domain. Currently renaming the GPOs is not supported
-and would need to be done manually.
-
-The domain rename is done in two steps: first, the 'samba-tool domain backup
-rename' command will clone the domain DB, renaming it in the process, and
-producing a backup-file. Then, the 'samba-tool domain backup restore' command
-takes the backup-file and restores the renamed DB to disk on a fresh DC.
-
-New samba-tool options for diagnosing DRS replication issues
-------------------------------------------------------------
-
-The 'samba-tool drs showrepl' command has two new options controlling
-the output. With --summary, the command says very little when DRS
-replication is working well. With --json, JSON is produced. These
-options are intended for human and machine audiences, respectively.
-
-The 'samba-tool visualize uptodateness' visualizes replication lag as
-a heat-map matrix based on the DRS uptodateness vectors. This will
-show you if (but not why) changes are failing to replicate to some DCs.
-
-Automatic site coverage and GetDCName improvements
---------------------------------------------------
-
-Samba's AD DC now automatically claims otherwise empty sites based on
-which DC is the nearest in the replication topology.
-
-This, combined with efforts to correctly identify the client side in
-the GetDCName Netlogon call will improve service to sites without a
-local DC.
-
-Improved samba-tool computer command
-------------------------------------
-
-The 'samba-tool computer' command allow manipulation of computer
-accounts including creating a new computer and resetting the password.
-This allows an 'offline join' of a member server or workstation to the
-Samba AD domain.
-
-Samba performance tool now operates against Microsoft Windows AD
-----------------------------------------------------------------
-
-The Samba AD performance testing tool traffic_reply can now operate
-against a Windows based AD domain. Previously it only operated
-correctly against Samba.
-
-DNS entries are now cleaned up during DC demote
------------------------------------------------
-
-DNS records are now cleaned up as part of the 'samba-tool domain
-demote' including both the default and --remove-other-dead-server
-modes.
-
-Additionally DNS records can be automatically cleaned up for a given
-name with the 'samba-tool dns cleanup' command, which aids in cleaning
-up partially removed DCs.
-
-samba-tool ntacl sysvolreset is now much faster
------------------------------------------------
-
-The 'samba-tool ntacl sysvolreset' command, used on the Samba AD DC,
-is now much faster than in previous versions, after an internal
-rework.
-
-Samba now tested with CI GitLab
--------------------------------
+NOTE WELL: The use of GnuTLS means that Samba will honour the
+system-wide 'FIPS mode' (a reference to the US FIPS-140 cryptographic
+standard) and so will not operate in many still common situations if
+this system-wide parameter is in effect, as many of our protocols rely
+on outdated cryptography.
-Samba developers now have pre-commit testing available in GitLab,
-giving reviewers confidence that the submitted patches pass a full CI
-before being submitted to the Samba Team's own autobuild system.
+A future Samba version will mitigate this to some extent where good
+cryptography effectively wraps bad cryptography, but for now that above
+applies.
-Dynamic DNS record scavenging support
--------------------------------------
+samba-tool improvements
+-----------------------
-It is now possible to enable scavenging of DNS Zones to remove DNS
-records that were dynamically created and have not been touched in
-some time.
+A new "samba-tool contact" command has been added to allow the
+command-line manipulation of contacts, as used for address book
+lookups in LDAP.
-This support should however only be enabled on new zones or new
-installations. Sadly old Samba versions suffer from BUG 12451 and
-mark dynamic DNS records as static and static records as dynamic.
-While a dbcheck rule may be able to find these in the future,
-currently a reliable test has not been devised.
+The "samba-tool [user|group|computer|group|contact] edit" command has been
+improved to operate more pleasantly on international character sets.
-Finally, there is not currently a command-line tool to enable this
-feature, currently it should be enabled from the DNS Manager tool from
-Windows. Also the feature needs to have been enabled by setting the smb.conf
-parameter "dns zone scavenging = yes".
+100,000 USER and LARGER Samba AD DOMAINS
+========================================
-CTDB changes
-------------
-
-There are many changes to CTDB in this release.
+Extensive efforts have been made to optimise Samba for use in
+organisations (for example) targeting 100,000 users, plus 120,000
+computer objects, as well as large number of group memberships.
-* Configuration has been completely overhauled
+Many of the specific efforts are detailed below, but the net results
+is to remove barriers to significantly larger Samba deployments
+compared to previous releases.
- - Daemon and tool options are now specified in a new ctdb.conf
- Samba-style configuration file. See ctdb.conf(5) for details.
+Reindex performance improvements
+--------------------------------
- - Event script configuration is no longer specified in the top-level
- configuration file. It can now be specified per event script.
- For example, configuration options for the 50.samba event script
- can be placed alongside the event script in a file called
- 50.samba.options. Script options can also be specified in a new
- script.options file. See ctdb-script.options(5) for details.
+The performance of samba-tool dbcheck --reindex has been improved,
+especially for large domains.
- - Options that affect CTDB startup should be configured in the
- distribution-specific configuration file. See ctdb.sysconfig(5)
- for details.
+join performance improvements
+-----------------------------
- - Tunable settings are now loaded from ctdb.tunables. Using
- CTDB_SET_TunableVariable=<value> in the main configuration file is
- no longer supported. See ctdb-tunables(7) for details.
+The performance of samba-tool domain join has been improved,
+especially for large domains.
- A script to convert an old-style configuration to a new one will be
- available for release but is not yet available.
+LDAP Server memory improvements
+-------------------------------
-* The following configuration variables and corresponding ctdbd
- command-line options have been removed and not replaced with
- counterparts in the new configuration scheme:
+The LDAP server has improved memory efficiency, ensuring that large
+LDAP responses (for example a search for all objects) is not copied
+multiple times into memory.
- CTDB_PIDFILE --pidfile
- CTDB_SOCKET --socket
- CTDB_NODES --nlist
- CTDB_PUBLIC_ADDRESSES --public-addresses
- CTDB_EVENT_SCRIPT_DIR --event-script-dir
- CTDB_NOTIFY_SCRIPT --notification-script
- CTDB_PUBLIC_INTERFACE --public-interface
- CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors
+Setting lmdb map size
+---------------------
- - The compile-time defaults should be used for the first 6 of these.
- - Use a symbolic link from the configuration directory to specify a
- different location for nodes or public_addresses (e.g. in the
- cluster filesystem).
- - Executable notification scripts in the notify.d/ subdirectory of
- the configuration directory are now run by unconditionally.
- - Interfaces for public IP addresses must always be specified in the
- public_addresses file using the currently supported format.
+It is now possible to set the lmdb map size (The maximum permitted
+size for the database). "samba-tool" now accepts the
+"--backend-store-size" i.e. --backend-store-size=4Gb. If not
+specified it defaults to 8Gb.
- Some related items that have been removed are:
+This option is avaiable for the following sub commands:
+ * domain provision
+ * domain join
+ * domain dcpromo
+ * drs clone-dc-database
- - The ctdb command's --socket command-line option
- - The ctdb command's CTDB_NODES environment variable
+LDB "batch_mode"
+----------------
- When writing tests there are still mechanisms available to change
- the locations of certain directories and files.
+To improve performance during batch operations i.e. joins, ldb now
+accepts a "batch_mode" option. However to prevent any index or
+database inconsistencies if an operation fails, the entire transaction
+will be aborted at commit.
-* Event scripts have moved to the scripts/legacy subdirectory of the
- configuration directory
+New LDB pack format
+-------------------
- Event scripts must now end with a ".script" suffix.
+On first use (startup of 'samba' or the first transaction write)
+Samba's sam.ldb will be updated to a new more efficient pack format.
+This will take a few moments.
-* The following service-related event script options have been
- removed:
+New LDB <= and >= index mode to improve replication performance
+---------------------------------------------------------------
- CTDB_MANAGES_SAMBA
- CTDB_MANAGES_WINBIND
+As well as a new pack format, Samba's sam.ldb uses a new index format
+allowing Samba to efficiently select objects changed since the last
+replication cycle. This in turn improves performance during
+replication of large domains.
- CTDB_MANAGES_CLAMD
- CTDB_MANAGES_HTTPD
- CTDB_MANAGES_ISCSI
- CTDB_MANAGES_NFS
- CTDB_MANAGES_VSFTPD
+Improvements to ldb search performance
+--------------------------------------
- CTDB_MANAGED_SERVICES
+Search performance on large LDB databases has been improved by
+reducing memory allocations made on each object.
- Event scripts for services are now disabled by default. To enable
- an event script and, therefore, manage a service use a command like
- the following:
+Improvements to subtree rename performance
+------------------------------------------
- ctdb event script enable legacy 50.samba
+Improvements have been made to Samba's handling of subtree renames,
+for example of containers and organisational units, however large
+renames are still not recommended.
-* Notification scripts have moved to the scripts/notification
- subdirectory of the configuration directory
+CTDB changes
+============
- Notification scripts must now end with a ".script" suffix.
+* nfs-linux-kernel-callout now defaults to using systemd service names
-* Support for setting CTDB_DBDIR=tmpfs has been removed
+ The Red Hat service names continue to be the default.
- This feature has not been implemented in the new configuration
- system. If this is desired then a tmpfs filesystem should be
- manually mounted on the directory pointed to by the "volatile
- database directory" option. See ctdb.conf(5) for more details.
+ Other distributions should patch this file when packaging it.
-* Support for the NoIPHostOnAllDisabled tunable has been removed
+* The onnode -o option has been removed
- If all nodes are unhealthy or disabled then CTDB will not host
- public IP addresses. That is, CTDB now behaves as if
- NoIPHostOnAllDisabled were set to 1.
+* ctdbd logs when it is using more than 90% of a CPU thread
-* The onnode command's CTDB_NODES_FILE environment variable has been
- removed
+ ctdbd is single threaded, so can become saturated if it uses the
+ full capacity of a CPU thread. To help detect this situation, ctdbd
+ now logs messages when CPU utilisation exceeds 90%. Each change in
+ CPU utilisation over 90% is logged. A message is also logged when
+ CPU utilisation drops below the 90% threshold.
- The -f option can still be used to specify an alternate node file.
+* Script configuration variable CTDB_MONITOR_SWAP_USAGE has been removed
-* The 10.external event script has been removed
+ 05.system.script now monitors total memory (i.e. physical memory +
+ swap) utilisation using the existing CTDB_MONITOR_MEMORY_USAGE
+ script configuration variable.
-* The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed
- As with other daemons, if ctdbd does not shut down when requested
- then manual intervention is required. There is no safe way of
- automatically killing ctdbd after a failed shutdown.
+REMOVED FEATURES
+================
-* CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration
- variable have been removed
+Web server
+----------
- These should be setup in the systemd unit/system file or, for SYSV
- init, in the distribution-specific configuration file for the ctdb
- service.
+As a leftover from work related to the Samba Web Administration Tool (SWAT),
+Samba still supported a Python WSGI web server (which could still be turned on
+from the 'server services' smb.conf parameter). This service was unused and has
+now been removed from Samba.
-* CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced
- 11.natgw and 91.lvs will no longer fail if
- CTDB_PARTIALLY_ONLINE_INTERFACES=yes. The incompatibility is,
- however, well documented. This option will be removed in future and
- replaced by sensible behaviour where public IP addresses simply
- switch interfaces or become unavailable when interfaces are down.
+samba-tool join subdommain
+--------------------------
-* Configuration file /etc/ctdb/sysconfig/ctdb is no longer supported
+The subdommain role has been removed from the join command. This option did
+not work and has no tests.
-GPO Improvements
-----------------
-The samba_gpoupdate command (used in applying Group Policies to the
-samba machine itself) has been renamed to samba_gpupdate and had the
-syntax changed to better match the same tool on Windows.
+Python2 support
+---------------
+Samba 4.11 will not have any runtime support for Python 2.
-REMOVED FEATURES
-================
+If you are building Samba using the '--disable-python' option
+(i.e. you're excluding all the run-time Python support), then this
+will continue to work on a system that supports either python2 or
+python3.
+To build Samba with python2 you *must* set the 'PYTHON' environment
+variable for both the 'configure' and 'make' steps, i.e.
+ 'PYTHON=python2 ./configure'
+ 'PYTHON=python2 make'
+This will override the python3 default.
+Except for this specific build-time use of python2, Samba now requires
+Python 3.4 as a minimum.
smb.conf changes
================
-As the most popular Samba install platforms (Linux and FreeBSD) both
-support extended attributes by default, the parameters "map readonly",
-"store dos attributes" and "ea support" have had their defaults changed
-to allow better Windows fileserver compatibility in a default install.
-
- Parameter Name Description Default
- -------------- ----------- -------
- map readonly Default changed no
- store dos attributes Default changed yes
- ea support Default changed yes
- full_audit:success Default changed none
- full_audit:failure Default changed none
-
-VFS interface changes
-=====================
-
-The VFS ABI interface version has changed to 39. Function changes
-are:
+ Parameter Name Description Default
+ -------------- ----------- -------
-SMB_VFS_FSYNC: Removed: Only async versions are used.
-SMB_VFS_READ: Removed: Only PREAD or async versions are used.
-SMB_VFS_WRITE: Removed: Only PWRITE or async versions are used.
-SMB_VFS_CHMOD_ACL: Removed: Only CHMOD is used.
-SMB_VFS_FCHMOD_ACL: Removed: Only FCHMOD is used.
+ allocation roundup size Default changed/ 0
+ Deprecated
+ client min protocol Changed default SMB2_02
+ server min protocol Changed default SMB2_02
+ mangled names Changed default illegal
+ web port Removed
+ fruit:zero_file_id Changed default False
-Any external VFS modules will need to be updated to match these
-changes in order to work with 4.9.x.
KNOWN ISSUES
============
-https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.9#Release_blocking_bugs
+https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.11#Release_blocking_bugs
#######################################
git.samba.org / samba.git / blobdiff