I completely disregarded the idea of using "safe" variables for the system call -- the reason is that you could say this about *any* variable used for a system call. I assumed that the ip address in question was defined in the script somewhere, especially since there was so little information given about the purpose of the script (not that there was a need for that information).
If you really want to look at how to secure perl scripts, there is a ton of documentation about what to do and what not to do. I'd point the way, but I don't remember what the way is. :) I don't write scripts that are used by the general public -- only co-workers. And if they enter 'rm -rf *', it's their own machine that they are hosing. :) ===== ------------------------------------ Jeffrey Hottle nkuvu at monkey yahoo dot com (remove the animal to email me!) __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://http://taxes.yahoo.com/ _______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
