Samba rebased to version 4.7.1
The _samba_ packages have been upgraded to upstream version 4.7.1, which provides a number of bug fixes and enhancements over the previous version. Notable changes include:
* Previously, the default value of the "rpc server dynamic port range" parameter was "1024-1300". With this update, the default has been changed to "49152-65535" and now matches the range used in Windows Server 2008 and later. Update your firewall rules if necessary.
* Samba now uses the Advanced Encryption Standard (AES) instruction set of Intel CPUs to accelerate Server Message Block (SMB) 3 signing and encryption operations.
* The options of the "ntlm auth" parameter have been extended. The parameter now accepts the "ntlmv2-only" (alias "no"), "ntlmv1-permitted" (alias "yes"), "mschapv2-and-ntlmv2-only", and "disabled" options. Additionally, the default value was renamed from "no" to "ntlmv2-only".
* The "smbclient" utility no longer displays a banner with the domain, operating system, and server version when connecting to a server.
* The default value of the "client max protocol" parameter has been changed to "SMB3_11". This enables utilities, such as "smbclient", to connect to servers using the SMB 3.11 protocol without setting the protocol version.
* For a better interoperability, Samba no longer supports using mixed minor versions in a *CTDB* cluster.
Samba automatically updates its tdb database files when the "smbd", "nmbd", or "winbind" daemon starts. Back up the database files before starting Samba. Note that Red Hat does not support downgrading tdb database files.
For further information about notable changes, read the upstream release notes before updating:
Besides including all the latest upstream bugfixes and interoperability improvements the new Samba version has MIT Kerberos support for AD and supports the new printing protocol MS-PAR (winspool).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.