Rahul:
You wrote:
On Thu, 18 Nov 2004 22:32:49 +0100, Christian Ziemski <czml1@xxxxxx> wrote:
Hello!
I think I found a serious bug in FC3's samba 3.0.8 pre1.3
Before I try to write it down I would like to ask:
Does it make sense to report a bug against the pre-release of samba when the final relase is out (but not yet as update for FC3)?
And should I report it here or directly in the samba.org list? (It's my first bug report for FC ...)
yes it makes sense to file a bug whenever you find regardless of the upstream status. You should file it at bugzilla.redhat.com against fc3/samba.
Redhat devels would either fix it themselves or propogate it to samba.org
I filed a bug report: Bug 139960: Windows client can access unshared(!) server directory
Copy of the report's text (for the interested ones):
I did some tries with a Windows2000 client connected to Samba installed on a FC3 box.
Here my simple smb.conf:
------------------------------------------------------
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2004/11/18 22:18:04 # Global parameters
[global]
workgroup = EBG-LAN
server string = Samba Server
security = SHARE
password server = None
username map = /etc/samba/smbusers
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = /etc/printcap
dns proxy = No
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
guest ok = Yes
hosts allow = 192.168.1., 127.
cups options = raw [homes]
comment = Home Directories [printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No [dvd]
path = /media/cdrom [share]
comment = Data2share
path = /home/share
read only = No [RPMS]
comment = FC3-RPMS
path = /FC3/RPMS
------------------------------------------------------(Since I have a German Windows installation I'm trying to translate the following names to the hopefully correct English ones.)
On the Windows2000 client I'm using Ontrack's PowerDesk 4.0.12.1 as file-manager (the problem seems to have to do with the client.)
In it I navigated to
"Network Neighbourhood"
"Whole Network"
"Microsoft Windows Network"
<my domain>
<my Samba server>
The Samba shares are shown as expected here.
Now I opened the context menu for one share after another to show the properties.
And here it happened: After opening the context menu of the share "RPMS" suddenly the file-manager listed an additional share: "rpm" with the contents of the directory /var/lib/rpm !!!
That only happens with that share.
Looking at /var/log/messages showed
: [2004/11/18 21:53:01, 0] smbd/service.c:make_connection(800) : nt02 (192.168.1.1) couldn't find service dv : [2004/11/18 21:53:01, 0] smbd/service.c:make_connection(800) : nt02 (192.168.1.1) couldn't find service dv : [2004/11/18 21:53:27, 0] smbd/service.c:make_connection(800) : nt02 (192.168.1.1) couldn't find service home : [2004/11/18 21:53:27, 0] smbd/service.c:make_connection(800) : nt02 (192.168.1.1) couldn't find service home
But those "couldn't find service" messages with the
by-one-character-crippled share names are only showing for the other
shares. The share "RPMS" ("expected" to be "rpm") here isn't.This effect/error doesn't happen with the original Windows Explorer, so I think it's a bug in PowerDesk too. (But Explorer lists the phantom share too, it just doesn't seem to be able to create it.) Anyway: Samba shouldn't give access to unshared directories!
Another interesting behaviour: When I reconfigure Samba and give the path "/home" to the initially empty share "homes" then the in PowerDesk newly listed share "rpm" doesn't contain /var/lib/rpm any longer but the directories under /home...
Christian
