You are reading in lines from a file named ship.cfg and you are not applying any particular attention to what is being read in. In perlspeak, the lines are "tainted". They could contain anything, usually benign, but possibly malicious.
Ordinarily, tainted data doesn't matter at all, as long as you content yourself to operations that don't have an effect outside the perl interpreter. But as soon as you reach out and start interacting with the system, whether it be disk, network or otherwise, tainting is of utmost importance.
The problem is that you are asking perl to use that unclean information read from ship.cfg to connect to a socket. And perl has a problem with that. It can't know whether what you are doing is benign, or whether you're trying to tie up a database listener or something crucial to your infrastructure. So until you untaint your data, it's not going to let you. Read up on perl security for information on untainting.
- another intruder with the mooring of the heart of the Perl
In reply to Re: using -T doesn't work (when attempting I/O)
by grinder
in thread using -T doesn't work
by tcf03
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |