Brent 'Dax' Royal-Gordon writes:

> My personal preference is for:
> 
>      $in=open :r "|/usr/bin/foo";
> 
> The pipe would be legal on either side of the string.  This would
> still allow the often-useful "type a pipe command at a prompt for a
> file", 

And it still allows for all those security holes in websites where
inexperienced programmers are just expecting a filename but write code
that's capable of executing commands.  Such behaviour is non-obvious to
somebody who hasn't been specifically warned about the danger, and the
potential for abuse is high.

Please let's not repeat this ...

Smylers

Reply via email to