Re: Breakage in samba security update?
On Wed, 18 Apr 2001, Dave Sherohman wrote: > Replying to myself, but... > > The server in question is an Alpha. Any attempt to connect to its workgroup > (for which it is the master browser) causes the following to appear in > /var/log/smb: > > [2001/04/18 10:48:55, 0] lib/util_sec.c:assert_gid(72) > Failed to set gid privileges to (-1,65534) now set to (0,0) uid=(0,0) Snap! :) I'm glad someone else had the same problem... Our AlphaServer runs Debian 'testing' and I found this error this morning... I solved it by manually installing the later 2.0.7-5 packages from ftp.uk.debian.org/debian/pool/main/s/samba :) Have fun! :) gdh
Re: Breakage in samba security update?
On Wed, Apr 18, 2001 at 10:28:29AM -0500, Dave Sherohman wrote: > Hey, folks... I just installed yesterday's samba update from security > (2.0.7-3.2) and none of my NT4 workstations can connect to it after the > upgrade, complaining of unspecified "network errors". I tried rebooting one > of them and it just got worse - that machine is now unable to communicate > with the entire workgroup containing the upgraded samba server. Replying to myself, but... The server in question is an Alpha. Any attempt to connect to its workgroup (for which it is the master browser) causes the following to appear in /var/log/smb: [2001/04/18 10:48:55, 0] lib/util_sec.c:assert_gid(72) Failed to set gid privileges to (-1,65534) now set to (0,0) uid=(0,0) [2001/04/18 10:48:55, 0] lib/util.c:smb_panic(2381) PANIC: failed to set gid Based on this, I am inclined to suspect a bug in the Alpha debs for the latest samba security patch; they appear to have been compiled with one or more incorrect options. Still digging into it, but solutions remain most welcome, of course. -- That's not gibberish... It's Linux. - Byers, The Lone Gunmen Geek Code 3.1: GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+ !K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+
Breakage in samba security update?
Hey, folks... I just installed yesterday's samba update from security (2.0.7-3.2) and none of my NT4 workstations can connect to it after the upgrade, complaining of unspecified "network errors". I tried rebooting one of them and it just got worse - that machine is now unable to communicate with the entire workgroup containing the upgraded samba server. I've checked smb.conf (it looks sane) and restarted samba manually. Where can I go from here, other than downgrading to the latest stable samba and giving up two sets of security patches? -- That's not gibberish... It's Linux. - Byers, The Lone Gunmen Geek Code 3.1: GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+ !K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+
