Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Software-update: Samba 4.3.0

Samba logo (60 pix)Versie 4.3 van Samba is uitgekomen. Dit programma draait op Unix-, BSD- en Linux-servers, en is een opensource-implementatie van het smb/cifs-netwerkprotocol. Sinds versie 3 kan Samba file- en printservices aan Windows-clients aanbieden en is het in staat om als domain controller te fungeren. Uitgebreide documentatie, inclusief praktische how-to's voor een iets oudere versie, kunnen op deze pagina worden gevonden. Met deze uitgave is ondersteuning voor versie 3 van Samba officieel komen te vervallen. De belangrijkste veranderingen in versie 4.3 zijn hieronder voor je op een rijtje gezet.

The logging code now supports logging to multiple backends. In addition to the previously available syslog and file backends, the backends for logging to the systemd-journal, lttng and gpfs have been added. Please consult the section for the 'logging' parameter in the smb.conf manpage for details.

Support for Apple's Spotlight has been added by integrating with Gnome Tracker.
For detailed instructions how to build and setup Samba for Spotlight, please see the Samba wiki.

New FileChangeNotify subsystem
Samba now contains a new subsystem to do FileChangeNotify. The previous system used a central database, notify_index.tdb, to store all notification requests. In particular in a cluster this turned out to be a major bottleneck, because some hot records need to be bounced back and forth between nodes on every change event like a new created file.
The new FileChangeNotify subsystem works with a central daemon per node. Every FileChangeNotify request and every event are handled by an asynchronous message from smbd to the notify daemon. The notify daemon maintains a database of all FileChangeNotify requests in memory and will distribute the notify events accordingly. This database is asynchronously distributed in the cluster by the notify daemons.
The notify daemon is supposed to scale a lot better than the previous implementation. The functional advantage is cross-node kernel change notify: Files created via NFS will be seen by SMB clients on other nodes per FileChangeNotify, despite the fact that popular cluster file systems do not offer cross-node inotify.
Two changes to the configuration were required for this new subsystem: The parameters "change notify" and "kernel change notify" are not per-share anymore but must be set globally. So it is no longer possible to enable or disable notify per share, the notify daemon has no notion of a share, it only works on absolute paths.

New SMB profiling code
The code for SMB (SMB1, SMB2 and SMB3) profiling uses a tdb instead of sysv IPC shared memory. This avoids performance problems and NUMA effects. The profile stats are a bit more detailed than before.

Improved DCERPC man in the middle detection for kerberos
The gssapi based kerberos backends for gensec have support for DCERPC header signing when using DCERPC_AUTH_LEVEL_PRIVACY.

SMB signing required in winbindd by default
The effective value for "client signing" is required by default for winbindd, if the primary domain uses active directory.

Experimental NTDB was removed
The experimental NTDB library introduced in Samba 4.0 has been removed again.

Improved support for trusted domains (as AD DC)
The support for trusted domains/forests has improved a lot.
samba-tool got "domain trust" subcommands to manage trusts:
  • create - Create a domain or forest trust.
  • delete - Delete a domain trust.
  • list - List domain trusts.
  • namespaces - Manage forest trust namespaces.
  • show - Show trusted domain details.
  • validate - Validate a domain trust.
External trusts between individual domains work in both ways (inbound and outbound). The same applies to root domains of a forest trust. The transitive routing into the other forest is fully functional for kerberos, but not yet supported for NTLMSSP.
While a lot of things are working fine, there are currently a few limitations:
  • Both sides of the trust need to fully trust each other!
  • No SID filtering rules are applied at all!
  • This means DCs of domain A can grant domain admin rights
  • in domain B.
  • It's not possible to add users/groups of a trusted domain
  • into domain groups.
SMB 3.1.1 supported
Both client and server have support for SMB 3.1.1 now.
This is the dialect introduced with Windows 10, it improves the secure negotiation of SMB dialects and features.
There's also a new optinal encryption algorithm aes-gcm-128, but for now this is only selected as fallback and aes-ccm-128 is preferred because of the better performance. This might change in future versions when hardware encryption will be supported. See here.

New smbclient subcommands
  • Query a directory for change notifications: notify <dir name>
  • Server side copy: scopy <source filename> <destination filename>
New rpcclient subcommands
  • netshareenumall - Enumerate all shares
  • netsharegetinfo - Get Share Info
  • netsharesetinfo - Set Share Info
  • netsharesetdfsflags - Set DFS flags
  • netfileenum - Enumerate open files
  • netnamevalidate - Validate sharename
  • netfilegetsec - Get File security
  • netsessdel - Delete Session
  • netsessenum - Enumerate Sessions
  • netdiskenum - Enumerate Disks
  • netconnenum - Enumerate Connections
  • netshareadd - Add share
  • netsharedel - Delete share
New modules
  • idmap_script - see 'man 8 idmap_script'
  • vfs_unityed_media - see 'man 8 vfs_unityed_media'
  • vfs_shell_snap - see 'man 8 vfs_shell_snap'
New sparsely connected replia graph (Improved KCC)
The Knowledge Consistency Checker (KCC) maintains a replication graph for DCs across an AD network. The existing Samba KCC uses a fully connected graph, so that each DC replicates from all the others, which does not scale well with large networks. In 4.3 there is an experimental new KCC that creates a sparsely connected replication graph and closely follows Microsoft's specification. It is turned off by default. To use the new KCC, set "kccsrv:samba_kcc=true" in smb.conf and let us know how it goes. You should consider doing this if you are making a large new network. For small networks there is little benefit and you can always switch over at a later date.

Configurable TLS protocol support, with better defaults
The "tls priority" option can be used to change the supported TLS protocols. The default is to disable SSLv3, which is no longer considered secure.

Samba-tool now supports all 7 FSMO roles
Previously "samba-tool fsmo" could only show, transfer or seize the five well-known FSMO roles:
  • Schema Master
  • Domain Naming Master
  • RID Master
  • PDC Emulator
  • Infrastructure Master
It can now also show, transfer or seize the DNS infrastructure roles:
  • DomainDnsZones Infrastructure Master
  • ForestDnsZones Infrastructure Master
CTDB logging changes
The destination for CTDB logging is now set via a single new configuration variable CTDB_LOGGING. This replaces CTDB_LOGFILE and CTDB_SYSLOG, which have both been removed. See ctdbd.conf(5) for details of CTDB_LOGGING.
CTDB no longer runs a separate logging daemon.

CTDB NFS support changes
CTDB's NFS service management has been combined into a single 60.nfs event script. This updated 60.nfs script now uses a call-out to interact with different NFS implementations. See the CTDB_NFS_CALLOUT option in the ctdbd.conf(5) manual page for details. A default call-out is provided to interact with the Linux kernel NFS implementation. The 60.ganesha event script has been removed - a sample call-out is provided for NFS Ganesha, based on this script.
The method of configuring NFS RPC checks has been improved. See ctdb/config/nfs-checks.d/README for details.

Improved Cross-Compiling Support
A new "hybrid" build configuration mode is added to improve cross-compilation support.
A common challenge in cross-compilation is that of obtaining the results of tests that have to run on the target, during the configuration phase of the build. The Samba build system already supports the following means to do so:
  • Executing configure tests using the --cross-execute parameter
  • Obtaining the results from an answers file using the --cross-answers
  • parameter
The first method has the drawback of inaccurate results if the tests are run using an emulator, or a need to be connected to a running target while building, if the tests are to be run on an actual target. The second method presents a challenge of figuring out the test results.
The new hybrid mode runs the tests and records the result in an answer file. To activate this mode, use both --cross-execute and --cross-answers in the same configure invocation. This mode can be activated once against a running target, and then the generated answers file can be used in subsequent builds.
Also supplied is an example script that can be used as the cross-execute program. This script copies the test to a running target and runs the test on the target, obtaining the result. The obtained results are more accurate than running the test with an emulator, because they reflect the exact kernel and system libraries that exist on the target.

Improved Sparse File Support
Support for the FSCTL_SET_ZERO_DATA and FSCTL_QUERY_ALLOCATED_RANGES SMB2 requests has been added to the smbd file server. This allows for clients to deallocate (hole punch) regions within a sparse file, and check which portions of a file are allocated.

Versienummer 4.3.0
Releasestatus Final
Besturingssystemen Linux, BSD, Solaris, UNIX
Website Samba
Bestandsgrootte 19,47MB
Licentietype GPL

Door Bart van Klaveren

Downloads en Best Buy Guide

09-09-2015 • 15:11

5 Linkedin Google+

Submitter: begintmeta

Bron: Samba


Reacties (5)

Wijzig sortering
Enige tijd geleden ben ik van Samba 3.6 naar 4.1 gegaan. Wat een drama! logfiles vol errors en niets dan problemen. Op de forums was ik bepaald niet de enige en daar werd ook al aangegeven dat 4.x nog verre van echt stabiel was. Snel weer terug gegaan naar 3.6 en alles draaide weer probleemloos.

Het zal me benieuwen hoe dat met 4.3 gesteld is. Als de support van Samba-3 wordt gestopt, dan zal ik op een gegeven moment toch de overstap moeten maken... :|
Da's ook niet zo raar, daar samba 3 en samba 4 te veel van elkaar verschillen.
Het is niet even knippen en plakken, je moet hem helemaal nalopen en veel dingen extra instellen...
Inderdaad - dat is wel vaker zo als je een major version bump doet van een stuk software. Zelfs bij een minor update is het aangeraden om je logs te controleren en 1 voor 1 problemen op te lossen.
Het zal me benieuwen hoe dat met 4.3 gesteld is. Als de support van Samba-3 wordt gestopt, dan zal ik op een gegeven moment toch de overstap moeten maken... :|
Hangt van je distributie af. Backports zijn er wellicht ook, bijvoorbeeld.
Dat is vreemd, ik kan die ervaring totaal niet delen. Moet zeggen dat hier prima draait op ubuntu 14.04.

Op dit item kan niet meer gereageerd worden.

Apple iPhone XS HTC U12+ dual sim LG W7 Google Pixel 3 XL OnePlus 6 Battlefield V Samsung Galaxy S10 Google Pixel 3

Tweakers vormt samen met Tweakers Elect, Hardware.Info, Autotrack, Nationale Vacaturebank en Intermediair de Persgroep Online Services B.V.
Alle rechten voorbehouden © 1998 - 2018 Hosting door True