Anyone who is on the Slackware security mailing list, you saw the Samba fix that came out a few days ago that resolved the DoS issue. But it mistakenly made Samba depend on dmapi.

Well, today another email went out, explaining how the new dependency was not intentional, and there was a new package that would resolve that issue.

That is my problem. I have installed the new package directly from the link given in the email, but Samba is still failing on the missing libdm file.

Anyone else having this problem?

I'm running Slackware 10.0 and I ended up having more that just libdm.so.0 missing. I had to install the following packages to get Samba back on its feet:

acl-2.2.34-i486-1.tgz
attr-2.4.28-i486-1.tgz
cyrus-sasl-2.1.22-i486-1.tgz
dmapi-2.2.3-i486-2.tgz
openldap-client-2.3.24-i486-1.tgz

I'm unsure whether xfsprogs would've fixed my issues, though. I was previously using Samba 3.0.10.

Incidentally, I didn't need xfsprogs to get libdm.so.0. Looks like it's also included in the dmapi package too.

my samba is totally broken now too

I cant even roll back these updates....drive image to the rescue I guess.

Well, glad I'm not the only one with this problem.

Perhaps "glad" isn't exactly the right word...

Pat must be banging his head on the wall. Or maybe it is just you and me LOL.

Are you guys sure you used the updated Samba package for Slackware 10.0 /10.1 / 10.2 and not for -current??? The packages in the respective /patches directories for the official releases are not linked to any of those packages mentioned in this thread as far as I can determine (using ldd).

Eric

Hi,

I only run slackware 10.2 on all my slackware box's. Current scares me.

I use slapt-get to fetch and apply updates as required.

I'm using the latest slapt-get; stable that is.

I'm using the primary mirror ((http://osuosl.org)

But I tell slapt-get to download them only for me, then I manually gpg verify them. e.g. "slapt-get --upgrade -d"

Then I have slapt-get perform the upgrades. "slapt-get --upgrade -s" to simulate, and make sure It's all good, then "slapt-get --upgrade"

The problem I get is, no KDE connection over lan. If I go to 'cli' and use "smbmount //" I get an error of "ERRDOS: directory tree structure does not exist" or something like that.

I then ran package tool, turned off samba to auto-load, rebooted. Then removed the packages, then rebooted. Put in the default slackware 10.2 samba on all the pc's, and they get the same error.

However, a windows PC can connect.

So basically now I'm just restoring all the slack boxen from images I made, then I'll put in my updates, less the samba. Then turn off the samba until I figure out what's going on.

Last weeks patch blew my printer share's on samba but I just got past that with making my print jobs pdf's then moved them over; but this is weird.

The pc's do ping each other too.

I went to slackware's site, and was thinking of sending him an email or see if he had an irc channel or something that he might idle, but couldnt find one.

But I dont see anyone else but me and MS3GFX getting this issue, so I figured maybe slapt-get is doing me wrong I dont know.

Please check that slapt-get installed samba-3.0.23-i486-2_slack10.2 for you. If your box got samba-3.0.23-i486-2 instead, the version from -current got inadvertantly installed.

Eric

Now I'm back to "isane" packetloss between linux clients using samba.

Windows talks but is really slow at first, about 20 second pause clicking on mapped network drive; but then does work so I'm assuming I'm getting loss on windows too.

I run slackware -current here and I had the same problem. I upgraded to samba-3.0.23-i486-2 (after reading this thread and congratulating myself on waiting this long ). I ended up having to install dmapi-2.2.3-i486-2 to get libdm installed. Here's the output from ldd for smbd:
Maybe a dodgy version of samba-3.0.23-i486-2 got to my mirror? I run my own mirror rsynced from slackware.mirrors.tds.net. But since it's working with dmapi-2.2.3-i486-2 I'm more confused than anything given the email about not needing libdm

Well, I think you're right about dmapi and that the Samba package in -current should not depend on it. IMO you can report this as a bug to volkerdi at slackware dot com and see what he has to say.

Eric

this is on a computer that was totally bamboozled, then I pulled out the patches, and went back to default install on.

presently getting packetloss to this machine.

maybe this helps to understand what I did,

Thanks for the advice. Just in case I had the wrong package, I checked the md5sum of my samba-3.0.23-i486-2.tgz against the slackware-security email and since they're the same I emailed Pat with the info (including a link to this thread).

Hi everyone - I received a reply from Pat about this. He pointed out that the slackware-security email states that the 10.0, 10.1, and 10.2 packages have been rebuilt on systems without the dm library. It doesn't mention the -current package in relation to libdm, only regarding reported problems with winbind. Also, the dmapi (and possible acl) packages will probably move to the A series in -current RSN since a lot of stuff is starting to depend on them.

The confusion for me was that I assumed the 10.2 changelog quote applied to -current. It doesn't and the -current changelog only has the following for Samba:
For me, installing dmapi-2.2.3-i486-2 to get libdm on my Slackware -current boxes got things back to normal. I don't have any other configurations (10.2 or earlier) to test against though...