Hello,
I've run into something that looks like a bug in samba security. I've seen it
both in 2.0.5a and now in 2.0.6. The problem is that filesystems mounted by
samba via autofs or mount do *not* honor file permissions.
For example, using autofs, I created an auto.hosts mount map entry called
"ray". It's defined as such:
ray -fstype=smb,username=ray,password=rays_passwd,uid=1501,gid=1501
://brazil/ray
Now, if I log in as another user, say ed, and cd to /net/ray, here's what I
see:
# ls -l /net
drwxr-xr-x 1 ray ray 512 Nov 12 18:05 ray
# ls -l /net/ray
-rwxr-xr-x 1 ray ray 151484 Nov 12 14:45 large_example.obf
drwxr-xr-x 1 ray ray 512 May 11 1999 matlab
drwxr-xr-x 1 ray ray 512 Mar 9 1999 public_html
-rwxr-xr-x 1 ray ray 16536 Nov 12 14:45 simple_example.obf
drwxr-xr-x 1 ray ray 512 Nov 11 13:01 tmp
drwxr-xr-x 1 ray ray 512 Nov 11 12:10 transfer
-rwxr-xr-x 1 ray ray 5617060 Nov 12 15:48 user_manual.pdf
The files are all owned by "ray", and ed does not have write permission. If
user ed then tries to edit a new file under /net/ray, this is appropriately
not permitted.
HOWEVER, if user ed tries to edit an existing file, permission is granted. In
short, other users are able to modify existing files.
Am I doing something silly here, or is there a problem with smbfs?
For reference, I'm running RedHat 6.1 with most updates. The smb host brazil
referenced above is the same Linux box that I'm running on.
TIA.
-Ray Kraft
--
Ray Kraft | Boeing Seattle | [EMAIL PROTECTED] | (425) 965-2015
GPG fingerprint: 95A4 2B62 DF72 CF2A 0639 6EA5 632D F5CF 44B3 DA81
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Windows95: win-doz-nin-te-fiv> n.
32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit
operating system originally coded for a 4 bit microprocessor, written by a
2 bit company that can't stand 1 bit of competition.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
