On Sat, 16 Oct 1999, Mike Nowlin wrote:
>
> > SUIDDIR will work for any user EXCEPT ROOT
> > I did this because I felt it was a security hole to allow users to create
> > files owned by root.
> > (from memory it will also refuse to do files that have the execute bit set
> > but I can't remembe
> SUIDDIR will work for any user EXCEPT ROOT
> I did this because I felt it was a security hole to allow users to create
> files owned by root.
> (from memory it will also refuse to do files that have the execute bit set
> but I can't remember for sure)
In a mildly drunken state, I respond.
On Fri, Oct 15, 1999 at 10:29:04AM -0700, Julian Elischer wrote:
> SUIDDIR will work for any user EXCEPT ROOT
Ahh I see, a big thanks to you Julian! OK, I'll use a different userid, say,
bar (and make the directory sticky so foo cannot remove the file it just
created - it will be owned by bar).
SUIDDIR will work for any user EXCEPT ROOT
I did this because I felt it was a security hole to allow users to create
files owned by root.
(from memory it will also refuse to do files that have the execute bit set
but I can't remember for sure)
We use it all the time on our PC fileservers so that
[Maybe this is -questions/-stable material, I'm not sure. Please flame
appropriately.]
On a very recent -stable system:
I have a directory, say /ftp/foocust/in. This directory
- resides in a filesystem mounted on /ftp with the suiddir option
(with SUIDDIR in the kernel).
- is owned by uid root
5 matches
Mail list logo