my $SSH = system "$ssh_cli $login $ip";
if ($SSH =~ /username/i) {
[download]

Sorry, this will not do what you expect. system waits until the command finishes, does not capture the command's output and does not allow interactive communication with the subprocess.

I would instead recommend the module Net::OpenSSH. Its documentation shows you how to integrate it with other modules such as Expect. Since you seem to want to connect to multiple remote machines to execute commands there, you might also take a look at Net::OpenSSH::Parallel (I haven't used it myself yet but I've heard good things).

without the possibility to install any module

I recommend you have a look at Yes, even you can use CPAN. If you really, really can't install any modules, you could have a look at my writeup on interacting with external commands here and you'd have to study perlipc, but I would strongly recommend you follow the above advice to use something like Net::OpenSSH instead. There was even a thread two days ago asking a question similar to yours, in which salva mentioned you can install it simply by copying over its lib directory.

Hi,

I think I am going to make test with th ling to perlipc. the main idea was to make one script to configure several builders according the builders (maybe more in the futur) following by the IP adress

Cisco    172.22.99.254
...
Extreme Networks    172.29.24.239
...
HP    172.28.127.245
...
Symbol Technologies, Inc.    10.150.238.1
[download]

for each, check if the symbole is > or # at the prompt and send lines for specifics builders.

I think I am going to make test with th ling to perlipc.

IPC can be tricky, especially interactive communication with processes on remote machines, as you seem to want to do. Let me put my advice a different way: I suspect the time you spend on getting the appropriate modules installed will be less than the time necessary to re-invent the IPC wheel.

Hello touriste75,

I would start with (How To Configure SSH Key-Based Authentication on a Linux Server).

Update: Forgot to say, by using SSH-keys you don't need to enter a password to connect to your remote host. Really you should do this even if you can use Perl modules.

As a second step a few days ago another Monk asked similar question, and he post a piece of code that seems to be working according to him (untested by me). Find more about it here (SSH and qx).

From the similar question (SSH and qx) as salva the author of Net::OpenSSH suggested: Net::OpenSSH is a pure Perl module. You just have to copy everything in the lib directory from the module distribution into some directory in the machine and add that directory into @INC to get it working..

Update2: In the past I had similar problems I tested any possible way of ssh, telnet modules that I could find. Take a look with working codes examples Best module to execute administrator commands on external operating systems (Linux).

Recently also another monk was asking for something similar (been able to SSH to multiple nodes). I created a working example for him with Net::OpenSSH::Parallel and the example is multiple machines disk space alert.

Similarly if you want to execute also SUDO commands, including example with working code Net::OpenSSH::Parallel with sudo commands.

Hope this helps, maybe to have another approach to your problem.

The Monks here were kind enough to help me get Net::OpenSSH installed on an older system where updates were, uh, problematic. But I was further stymied by the age of the underlying ssh client, which was incompatible. So I offer the following:

sub ops_do_ssh_qx {
   my ($cmd) = @_;

   $cmd->{ssh_cmd} = 'ssh ' .  $cmd->{user} . '\@' . $cmd->{host} . ' 
+\'' . $cmd->{command} . '\'' . ' 2>/dev/null';

   $cmd->{output} = qx($cmd->{ssh_cmd});
   if ( defined $cmd->{output} ) {
      $cmd->{cmd_ret_code} = $?;
      chomp $cmd->{output};
   }
   else {
      ($cmd->{ssh_ret_code}, $cmd->{ssh_ret_msg}) = (0 + $!, '' . $!);
   }

   return $cmd;
}
[download]

It does rely on ssh keys being setup properly.

I hope you find it useful.

Thanks,
cbeckley

my goal is to connect in SSH to several material and without the result in STDOUT, pass in console some command.

It is even more simple than what you tried. Sample transcript:

qwurx [shmem] ~> perl -e 'open my $fh,"|-","ssh localhost"; while(<STD
+IN>){print $fh $_}'
Pseudo-terminal will not be allocated because stdin is not a terminal.

The programs included with the Debian GNU/Linux system are free softwa
+re;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You have new mail.
touch blorflydick   <--- input at terminal
touch gobbledygook  <--- input at terminal
^D                  <--- input at terminal (Ctrl-D or eof)
qwurx [shmem] ~> ls -lrt | tail -2 <--- after perl terminated
-rw-r--r--  1 shmem shmem         0 Mar 15 18:30 blorflydick
-rw-r--r--  1 shmem shmem         0 Mar 15 18:30 gobbledygook
[download]

No modules required. If you just want to pass some commands and don't care about STDOUT/STDERR, all you have to do is a plain piped open. If you want to multiplex the commands to several hosts, store the filehandles in an array and print your input to the remote shells in a loop (untested):

my @fh;
for my $ip (@ips) {
    open my $fh,"|-","ssh $ip" or die "Can't ssh to $ip: $!\n";
    push @fh, $fh;
}
while (<STDIN>) {
    for my $fh (@fh) {
        print $fh $_;
    }
}
[download]

You might, since you are not interested in STDOUT/STDERR, redirect all output within the piped open to avoid funny blocking errors and/or spamming your terminal:

    open my $fh,"|-","ssh $ip >/dev/null 2>&1" or die "Can't ssh to $i
+p: $!\n";
[download]

and/or set $|=1 (see perlvar) and/or call $fh->autoflush on every handle created. Finding out the difference between these measures is left as an excercise to the reader.

update: the ssh connection in this example was established using ssh keys and a running ssh-agent. If you have to enter (different) credentials you want to set $fh->autoflush and use sshpass to pass the passwords (for each connection).

The issue is that ssh doesn't read the password from STDIN but directly from the tty and Perl doesn't offer a way to manipulate ttys/ptys without using some non core module.