Re: gpilotd & corba

[Michael Fulbright <msf redhat com>]

deity@trinity.dbc.bib.dk said:
> 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
> gpilotd will read these upon sync. (any security issues here that I'm
> missing ?) 

If this directory has a predictable name, cant some nasty person take
advantage of this (like all the /tmp exploits recently discussed)?

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.

Dr Mike