in reply to Future security worries?

Just to add to the other comment. suidperl was only necessary on platforms where (secure) setuid scripts were not available so it is possible that you would have not needed it in the first place. If you do not have setuid scripts on your system then an alternative to suidperl (or indeed sudo ) would be to use a small C wrapper like:
#include <unistd.h> int main( int argc, char **argv) { execv("./foo.pl", argv); }
and make the executable setuid as appropriate. I would, however, be cautious using the above code lest you should unintentionally allow someone to run any program on the system as root: you would want to be absolutely sure that no-one would be able to replace the code of "foo.pl" with something unintended as the very first thing. You should also ensure that any program thus wrapped has taint mode on with the '-T' on the shebang line.
/J\