-Original Message-
From: Linda Walsh [mailto:sa...@tlinx.org]
Sent: 20 June 2011 04:24
To: David Aldrich; Samba mailing list
Subject: Re: Sticky bit problem
Linda Walsh wrote:
David Aldrich wrote:
Hi
We are building a Linux app under Centos 5.3, using gnu make 3.81 and
Hi
We are building a Linux app under Centos 5.3, using gnu make 3.81 and gcc 4.12.
The working directory is on a remote machine and is either a Samba share or a
Windows 7 share. We find that in the case of a Windows 7 share the resulting
executable has the sticky bit set in group:
On
Hi
We are building a Linux app under Centos 5.3, using gnu make 3.81 and gcc 4.12.
The working directory is on a remote machine and is either a Samba share or a
Windows 7 share. We find that in the case of a Windows 7 share the resulting
executable has the sticky bit set in group:
On
David Aldrich wrote:
Hi
We are building a Linux app under Centos 5.3, using gnu make 3.81 and gcc 4.12.
The working directory is on a remote machine and is either a Samba share or a
Windows 7 share. We find that in the case of a Windows 7 share the resulting
executable has the sticky bit
Linda Walsh wrote:
David Aldrich wrote:
Hi
We are building a Linux app under Centos 5.3, using gnu make 3.81 and
gcc 4.12. The working directory is on a remote machine and is either
a Samba share or a Windows 7 share. We find that in the case of a
Windows 7 share the resulting executable
Hi all.
I configured a samba share:
;-
[soft]
comment = Software
browseable = yes
path = /mnt/soft
writable = no
write list = nikitin stiven @root
public = yes
create mode = 0664
directory mode = 1757
Problem is, with standard unix permissions, renaming a file is a matter of
writing to the directory. You can have a file owned by root:root and chmodded
to 000, and any non-priveledged user would still be able to rename that file
if they had write access to the directory. If a user has enough
jef dodson wrote:
I have a question about samba and sticky bits. I have a share with the
following configuration:
[documents]
comment = documents
path = /shares/documents
public = no
writeable = yes
printable = no
valid users = lan1
force user = docadmin
Yura Pismerov wrote:
jef dodson wrote:
I have a question about samba and sticky bits. I have a share with the
following configuration:
[documents]
comment = documents
path = /shares/documents
public = no
writeable = yes
printable = no
valid users = lan1
ok, that works to disallow non-owners from renaming the file, but what I would
like to do is disallow EVERYONE ( including the owner of the file ) from
editing, moving, or changing the filename once it is created. the only person
who should be able to make those changes is a special user. any
jef dodson wrote:
ok, that works to disallow non-owners from renaming the file, but what I would
like to do is disallow EVERYONE ( including the owner of the file ) from
editing, moving, or changing the filename once it is created. the only person
who should be able to make those changes
11 matches
Mail list logo
