Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Re^6: Splitting up quoted/escaped command line arguments

by Tommy (Chaplain)
on Feb 11, 2014 at 22:16 UTC ( #1074528=note: print w/ replies, xml ) Need Help??

in reply to Re^5: Splitting up quoted/escaped command line arguments
in thread Splitting up quoted/escaped command line arguments

Because it's obvious they have been written to be parsed by a shell.

OK, no problem, I'll repeat myself in case you missed it in my earlier response to this issue. It's already assumed that a shell is going to be used on the remote side of the connection (as in the OP). There's nothing in the OP that would be interpreted as a shell escape locally; even if there were shell escapes present--passing it to exec in indirect object notation negates the possibility that it gets sent to the shell because each argument is passed as a literal argument to the invocant. Remote shell: yes. Localhost: no. It is the local machine where the shell is to be avoided.

Can you assure that there would be no entries using redirections, pipes, back-quotes, logical operators, variables, wildcards, etc.?

Yes. Actually that is assured. Anything like that is supposed to be wrapped in a shell script and sent+executed on the remote host. Still, this is a moot point because of the specific way I'm calling exec.

A mistake can be valuable or costly, depending on how faithfully you pursue correction

Comment on Re^6: Splitting up quoted/escaped command line arguments

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1074528]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (8)
As of 2015-10-07 17:59 GMT
Find Nodes?
    Voting Booth?

    Does Humor Belong in Programming?

    Results (195 votes), past polls