Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Made Proc::Daemon internally taint safe by untainting pids read from any external source. #2
Also, added a new test which re-runs the primary 02_testmodule.t in taint mode. (I only tested on linux so hopefully this works in non-unix environments like Win32).
I added a comment in the pod to indicate that Proc::Daemon is now taint safe if not passed any tainted parameters. That is to say that Proc::Daemon will no longer be the source of any tainted data, particularly from get_pid (as it used to). However, since it uses commands like 'chdir' and 'exec' internally, you might still get a fatal error in taint mode if you pass it tainted data. That seems reasonable to me since Proc::Daemon has no safe way of untainting such data; it should therefore be the caller's responsibility.