the arguments that need to be passed come from user-supplied data, and while the program being called itself should be safe to invoke, there's the issue of the shell and its shenanigans ... system and exec have "safe" invocations ... Does qx//?
No, not in the core*. I wrote about exactly this issue here: In this case, I might recommend IPC::System::Simple's capturex as a safer drop-in replacement for qx//, or IPC::Run3 if you want to capture STDERR as well.
* Update: Ok, well, not quite right, there are piped opens with more than one argument, but those require one to be careful to get right, and didn't work on Windows for quite some time. The modules just make this much easier.
In reply to Re: Safely capturing the output of an external program
by haukex
in thread Safely capturing the output of an external program
by AppleFritter
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |