You don't really need a trusted host relationship, you just need passwordless keys. If passwordless keys are impossible, then you will have to use the interactive method. Maybe you can go forward by hacking Net::Ssh::Perl to redirect the STDOUT part of the connection. Looking into the source of Net::SSH::Perl::SSH1, there seem to be handlers like SSH_SMSG_STDOUT_DATA and replacing the default handler with something that doesn't accumulate the string might help:
# Original code
sub cmd {
...
unless ($ssh->handler_for(SSH_SMSG_STDOUT_DATA)) {
$ssh->register_handler(SSH_SMSG_STDOUT_DATA,
sub { $ssh->{_cmd_stdout} .= $_[1]->get_str });
}
...
}
I would try to supply my own callback like this:
my $ssh = Net::SSH::Perl->new(...);
open my $outfh, ">", $filename
or die "Couldn't create '$filename' : $!";
binmode $outfh;
$ssh->register_handler('stdout', sub { print $outfh $_[1]; });
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|