On Wed, Jan 15, 2014 at 14:25, David Sticht wrote: > Understanding the risks I am wanting to either allow the www user right to > open tty or change the user running the apache daemon. I am developing a > suite of intranet tools with perl to perform some network diagnostics. > Does anybody have a suggestion to move me in the right direction?
Build a small daemon that does whatever it is needs doing, run it as a user with the correct privileges, then have the www user talk to that via a socket.
