Hide Forgot
_samba_ rebased to version 4.4.4 The _samba_ packages have been upgraded to upstream version 4.4.4, which provides a number of bug fixes and enhancements over the previous version: * The WINS nsswitch module now uses the *libwbclient* library for WINS queries. Note that the "winbind" daemon must be running to resolve WINS names that use the module. * The default value of the "winbind expand groups" option has been changed from "1" to "0". * The "-u" and "-g" options of the "smbget" command have been replaced with the "-U" option to match other Samba command's parameter. The "-U" option accepts a "username[%password]" value. Additionally, the "username" and "password" parameters in the "smbgetrc" configuration file have been replaced with the "user" parameter. * The "-P" parameter of the "smbget" command has been removed. * Printing using the "CUPS" back end with Kerberos credentials now requires to install the _samba-krb5-printing_ package and to configure CUPS appropriately. * It is now possible to configure Samba as a print server by using the CUPS back end with Kerberos credentials. To do so, install the _samba-krb5-printing_ package and configure CUPS appropriately. * Samba and CTDB header files are no longer installed automatically when you install _samba_. Samba automatically updates its tdb database files when the "smbd", "nmbd", or "winbind" daemon starts. Back up the databases files before starting Samba. Note that Red Hat does not support downgrading tdb database files. Note that using the Linux kernel CIFS module with SMB protocol 3.1.1 is currently experimental and the functionality is unavailable in kernels provided by Red Hat. For further information about notable changes, read the upstream release notes before updating: * https://www.samba.org/samba/history/samba-4.3.0.html * https://www.samba.org/samba/history/samba-4.4.0.html
Besides including all the latest upstream bugfixes and interoperability improvements the new Samba version contains e.g a GnuTLS based backupkey implementation which integrates Samba better with the systems crypto libraries instead of doing the crypto on its own. Newer file-server feature might be meeded by the storage team in one of their upcoming products.
winbindd does not list group memberships for display purposes (e.g. getent group ) anymore by default in Samba 4.2.0 and newer. The new default is "winbind expand groups = 0" now, the reason for this is the same as for "winbind enum users = no" and "winbind enum groups = no". Providing this information is not always reliably possible, e.g. if there are trusted domains.
smbget ------ The -u and -p options for user and password were replaced by the -U option that accepts username[%password] as in many other tools of the Samba suite. Similary, smbgetrc files do not accept username and password options any more, only a single "user" option which also accepts user%password combinations. The -P option was removed.
WINS nsswitch module -------------------- The WINS nsswitch module has been rewritten to address memory issues and to simplify the code. The module now uses libwbclient to do WINS queries. This means that winbind needs to be running in order to resolve WINS names using the nss_wins module. This does not affect smbd.
For the record, the current plan is to rebase to Samba 4.4.4 (released today): https://www.samba.org/samba/history/samba-4.4.4.html
smbspool_krb5_wrapper --------------------- To be able to print with CUPS using Kerberos credentials you need to install the samba-krb5-printing package and configure CUPS appropriately.
As with every Samba release, upgrades of tdb files are supported but not downgrades. Customers need to backup tdb files. Check earlier releases for the text.
Public headers -------------- Several public headers are not installed any longer. They are made for internal use only. More public headers will very likely be removed in future releases. Also public CTDB header files are no longer installed, since Samba and CTDB are built from within the same source tree.
We know about some regressions but they will be documented. VERFIED as part of qa process.
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. https://rhn.redhat.com/errata/RHBA-2016-2468.html