Slackware 10.0 / 10.1 / 10.2 / current : Samba 2.0.23 repackaged (SSA:2006-200-01)

This script is Copyright (C) 2006-2013 Tenable Network Security, Inc.


Synopsis :

The remote Slackware host is missing a security update.

Description :

New Samba packages are available for Slackware 10.0, 10.1, 10.2, and
-current. In Slackware 10.0, 10.1, and 10.2, Samba was evidently
picking up the libdm.so.0 library causing a Samba package issued
primarily as a security patch to suddenly require a library that would
only be present on the machine if the xfsprogs package (from the A
series but marked 'optional') was installed. Sorry -- this was not
intentional, though I do know that I'm taking the chance of this kind
of issue when trying to get security related problems fixed quickly
(hopefully balanced with reasonable testing), and when the fix is
achieved by upgrading to a new version rather than with the smallest
patch possible to fix the known issue. However, I tend to trust that
by following upstream sources as much as possible I'm also fixing some
problems that aren't yet public. So, all of the the 10.0, 10.1, and
10.2 packages have been rebuilt on systems without the dm library, and
should be able to directly upgrade older samba packages without
additional requirements. Well, unless they are also under /patches.

-) All the packages (including -current) have been patched with a fix
from Samba's CVS for some reported problems with winbind. Thanks to
Mikhail Kshevetskiy for pointing me to the patch. I realize these
packages don't really fix security issues, but they do fix security
patch packages that are less than a couple of days old, so it seems
prudent to notify slackware-security (and any subscribed lists) again.
Sorry if it's noise...

See also :

http://www.nessus.org/u?b8f00849

Solution :

Update the affected samba package.

Risk factor :

High

Family: Slackware Local Security Checks

Nessus Plugin ID: 22081 ()

Bugtraq ID:

CVE ID: