Re^3: safely passing args through ssh

That doesn't look anything like what I wrote. I showed how to contruct a shell command to pass to ssh but you passed 5 arguments after the target, none of which a shell command.

If you call ssh twice, you have two shell commands to build.

sub text_to_shell_lit(_) {
   return $_[0] if $_[0] =~ /^[a-zA-Z0-9_\-]+\z/;
   my $s = $_[0];
   $s =~ s/'/'\\''/g;
   return "'$s'";
}

my $very_remote_cmd = join ' ', map text_to_shell_lit,
  argcount => ( 'a b c' );

my $remote_cmd = join ' ', map text_to_shell_lit,
  ssh => ( '--', $very_remote_target, $very_remote_cmd );

backticks(ssh => ( '--', $remote_target, $remote_cmd ));
[download]

Comment on Re^3: safely passing args through ssh Select or Download Code

Replies are listed 'Best First'.
Re^4: safely passing args through ssh by perl5ever (Pilgrim) on Jul 25, 2011 at 23:02 UTC
Well, then I guess you didn't solve the problem that I stated.	[reply]
Re^5: safely passing args through ssh by ikegami (Patriarch) on Jul 25, 2011 at 23:29 UTC
The problem you stated: "what's a good way of encoding ... so that it will survive an ssh call?" Where "D" is the shell's literal parser and "s" is an arbitrary shell command, you want a function "E" that exhibits the following behaviour: `s = D(E(s)) = D(D(E(s))) = D(D(D(E(s)))) etc` [download] but there is none.	[reply] [d/l]
Re^6: safely passing args through ssh by perl5ever (Pilgrim) on Jul 26, 2011 at 14:56 UTC
Why are you ignoring the entire section of my original post starting with "To be specific about the problem ..."??? I'm not looking to encode an arbitrary shell command. Given an `$array` that will invoke a perl interpreter via `open(..., "-\|", @$array)` I am looking for ways to safely encode a perl script that will be passed to the interpreter via the command line.	[reply] [d/l] [select]
Re^7: safely passing args through ssh by ikegami (Patriarch) on Jul 26, 2011 at 18:03 UTC