in reply to Re^6: Doubt in perl taint
in thread Doubt in perl taint

I have presented a simplified version of the investigations we made - as a direct consequence of which, a multi-million pound project was delivered on time ... just.

BTW, I notice in your example, you run in the CWD and invoke via ./ - have you tried running your script in e.g. $HOME, setting the permissions on /usr/bin to 0755, putting /usr/bin on your path (if it isn't there already) and invoking relatively using $PATH e.g. invocation by `ls`; as in the OP ?

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^8: Doubt in perl taint
by ikegami (Patriarch) on Dec 14, 2008 at 01:58 UTC
    While it has to be more permissive than 755, I stand corrected.
    $ cp /bin/ls /tmp/ikegami/ $ chmod 777 /tmp/ikegami/ $ chmod 700 /tmp/ikegami/ls $ perl -T -e'%ENV=(PATH=>"/tmp/ikegami/"); system("ls") and die("error +: $?");' Insecure directory in $ENV{PATH} while running with -T switch at -e li +ne 1.

    (I used /tmp since I don't have root access.)