Samba security Prob

VorteX24 · n00b Joined: 03 Aug 2002 Posts: 14

My first problem: i recognized that i can look at every share of my samba server (acts as pdc) from a client that isnt authed by the domain server (samba). i mean, i can login as localadmin on a win2000 workstation, and look at samba shares that should be watchable to domain users. have a look at my conf:
http://suq.dyndns.org/~florian/smb.conf

then another problem: if i install any newer version of samba as 2.2.5-r1, i get the following error in the /var/log/samba/log.<user> users logfile (some thousands an hour like this).
ERROR: string overflow by 4 in string_sub(%u, 7)
[2002/11/21 12:23:43, 0] lib/util_str.c:string_sub(1219)

samba looks like running, but the users doesnt see any shares and cannot auth.

Thanks alot!

VorteX24 · n00b Joined: 03 Aug 2002 Posts: 14

*push*

Lin_Matt · Posted: Thu Nov 21, 2002 6:17 pm Post subject:

hmmm.... gonna take this step-by-step here...

LosD · Posted: Sat Nov 23, 2002 3:01 pm Post subject:

My Samba works, but I have the problem with samba flooding my /var/log/everything with

Nov 23 15:58:59 [smbd] ERROR: string overflow by 4 in string_sub(%H, 15)
Nov 23 15:58:59 [smbd] [2002/11/23 15:58:59, 0] lib/util_str.c:string_sub(1219)

In fact so often that metalog logrotates every second!

It began when I emerged samba 2.2.7, do anybody have a reason/solution?

Thx,
Dennis

VorteX24 · n00b Joined: 03 Aug 2002 Posts: 14

jep got same problem

LosD, got you a smp system? i got one two, perhaps could this be the reason ?

LosD · Posted: Sun Nov 24, 2002 4:48 pm Post subject:

Nope, just a single processor... I think it has something to do with the clients, because if I look in /var/log/samba/log.* it happens for some of the clients... One of the problems I think happened when I renamed my server from 'dserver' to 'tux'...

The client had a network drive which still referred to the server as dserver, and it was still able to connect to the server, even after reboot of the client, but it seems it made the server log errors (and the smbd processes spawned for the client only killable with -9/-SIGKILL)...

But it also happens for a few other clients, which do not have network drives connected to the server (and has string overflows by 8 and 9), so this isn't the only problem...

I have filed a bug report on bugs.samba.org, I am looking forward to see if it's known, and if it's indeed a bug, or if it's a configuration problem... I'll post the answer here....

Dennis

VorteX24 · n00b Joined: 03 Aug 2002 Posts: 14

emerge -u world
theres an depency thats necessary, dunno what dep., but after emerge -u world, new samba works