If you use RSA keys, scp can run non-interactively. If you make
statically compiled binaries of ssh, scp, etc then you could just upload
them to your $HOME/bin and use them from there. I've done this in the
past, but I had shell access to the machine so it was a bit easier. The
admin there was also too lazy/ignorant to install ssh, so I just installed
my own ;)
Encrypting the files with perl is a good idea as well, since they could be
crypted then downloaded from FTP without worries. This wouldn't require
opening or utilizing ports that may be firewalled. THere should be plenty
of examples in perldoc for doing this.
--Henry
On Tue, 2 Jan 2001, Pedro Zorzenon Neto wrote:
> On Tue, Jan 02, 2001 at 10:20:26AM -0800, Tom Marshall wrote:
> > Can you use FTP to put precompiled ssh and scp binaries on the machine?
> > $HOME/bin is usually a good place. I've done this before with some success.
> >
> > ---
> > The most effective Windows NT remote management tool? A car.
> >
> The remote machine is a web server with postgres.
> On the remote machine, I can use only ftp to put/retrieve data.
> This machine does't have telnetd, so... no logins...
> Other ports than 20,21,80 are firewall protected.
>
> As an workaround I can change by ftp my crontab over there and the commands are
>executed!!! :-) I don't need telnet anymore!!!
>
> I think 'scp' is not possible because it asks my password interactively...
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
