QUOTE (vividere @ May 4 2009, 02:24 PM)

Thanks for the feedback. Apparently the app was written in a cloistered environment where they don't have the noexec option on their /tmp directory so this probably wasn't discovered when running the app in their environment.
I am waiting to find out if the client can or will get the author to change the location to execute from. Could they use their own /tmp directory vs. the server /tmp directory, or are they the same directory?
If an executable was going to be spawned vs. ran where installed, what would the appropriate directory be?
Thanks
You can do per-user tmp directories(http://www.wlug.org.nz/PerUserTempDirs), but I couldn't tell you what impact it would have on other applications. Likely none, but you never know. If the solution isn't in production, or is a flexible, you can try it out.
http://www.wlug.org.nz/PerUserTempDirsMost developers are willing to accept input, especially if it'll make their applications more secure. Sometimes they'll build the application where the tmp file locations can be set at runtime.
I don't recommend it, but if it's preventing you from providing the solution your customer needs, then you may need to drop the noexec flag. If you do need to resort to this, try to reduce the amount of opportunities outsiders have to manipulate the tmp files.