Marcus Brinkmann <[EMAIL PROTECTED]> writes: > > The strangeness kicks in when the files are created in /tmp. No matter > > who I rmauthed from, the files will appear owned by user and group root > > with the default umask. This means that I can 'cat > /tmp/somefile', > > and actually get what I want in there, but I will not be able to open > > this file for writing again, as it is now writable only for root. > > What else could it do, without further support in the filesystem server for > this? :)
Well, it could refuse to create any files by default. And then have some mechanism for making exceptions to this rule. An example of such a mechanism (which I don't know if it makes sense): If the directory is writable by no-user processes, and if it has the setuid bit set, then the no-user process can create files, and the created files get the same owner as the directory. /nisse
