On 2002-09-15 04:12:24-0800, Ethan Benson wrote:
> you are wrong, sticky directories check the ownership of the file and
> only allow unlink() if the file owner matches the uid of the user
> attempting unlink(), or if the user owns the sticky directory, or the
> user is root. the file's permissions have absolutly nothing to do
> with it.
Apparently Linux differs from Solaris in this respect (which seems to be
where I remembered the semantics from):
merry:/tmp% uname -a
SunOS merry 5.8 Generic sun4m sparc
merry:/tmp% id
uid=100(wsl) gid=1(other) groups=1(other)
merry:/tmp% ls -l foo
-rw-rw-rw- 1 nobody nobody 4 Sep 15 17:12 foo
merry:/tmp% rm foo
merry:/tmp% ls -l foo
foo: No such file or directory
Solaris disallows unlinking other people's symlinks though.
Again, I apologize for the noise.
> from chmod(1)
>
> [snip]
from shred(1)
CAUTION: Note that shred relies on a very important assumption: that
the filesystem overwrites data in place. This is the traditional way
to do things, but many modern filesystem designs do not satisfy this
assumption. The following are examples of filesystems on which shred
is not effective:
* log-structured or journaled filesystems, such as those supplied with
AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)
^^^
Manpages aren't always 100% reliable (although your excerpt was certainly
correct).
Regards,
--
wsl@xxxxxxxxxxxx
|