Re: gpilotd & corba



On Wed, 16 Sep 1998, Michael Fulbright wrote:

> > 4) Currently, I'll store all requests as files /var/spool/gpilotd/
> > $USER/, and let the name/contents indicate what to do, and the forked
> If this directory has a predictable name, cant some nasty person take
> advantage of this (like all the /tmp exploits recently discussed)?

Well, if the gpilotd writes the requests to /var/spool/gpilotd/drmike,
which has mod drwx------, and gpilotd upon sync, forks and setuids to you,
I think it will be quite secure, but then again, I'm no master cracker.

> At a minimum I guess you just take a look at the existing path and make
> sure its really setup like you want before you use it.

What do you mean ?

eskil
---



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]