You make a good point, but I don't think the safety problem is reducible to "If I don't think its safe...". Just scan the web for all the people who innocently rooted themselves because they had a typo in an rm command and a foolish OS distro that didn't no-op rm / by default.
While it is true that, by nature, Perl sometimes needs to be executed to be syntax checked, that does not necessarily preclude the use of sand-boxing techniques. For instance, a call that writes to files through a Perl library isn't (usually) needed to evaluate code further down the line. Couldn't the perl syntax checker have been/be designed to monitor certain system calls and no-op them unless a flag was explicitly set to do otherwise?
Best, beth
In reply to Re^2: What restrictions are there on code execution when running perl in syntax check mode?
by ELISHEVA
in thread What restrictions are there on code execution when running perl in syntax check mode?
by ELISHEVA
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |