Valeriu Mutu wrote:
On Thu, May 08, 2008 at 07:33:13AM +0200, Peter Boosten wrote:
Vince Sabio wrote:
Note if you choose to do this: scp'ing files becomes a four-step process
(i.e., scp file(s) to intermediate server, log in to intermediate server,
scp to destination server, delete file(s) from intermediate server). Still
worth it, though.
Never thought of port forwarding?
Following Peter's idea and assuming that public key authentication is setup,
the tunnel could be setup as easy as:
ssh -f -L localhost:3333:localhost:4444 [EMAIL PROTECTED] "ssh -f -L
localhost:4444:localhost:22 [EMAIL PROTECTED] sleep 120"
In this case, we setup a tunnel through machineA to machineB.
No, I was more thinking of:
ssh -L 4444:your.own.host:22 [EMAIL PROTECTED]
and then open a new shell:
scp -P 4444 the-file-you-want-to-copy [EMAIL PROTECTED]:
This works easiest with agent forwarding, but I guess any authentication
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"