On 08:48 26 Jan 2003, Ed Wilts <[EMAIL PROTECTED]> wrote:
| On Sun, Jan 26, 2003 at 07:15:02PM +1100, Cameron Simpson wrote:
| > If you have an ssh-agent and forward it you can probably go:
| >
| > ssh hostA scp /tmp/file hostB:/tmp/file
| >
| > i.e. ssh to hostA and tell it to scp directly to hostB; the
| > forwarded connection will supply the right credentials.
|
| The problem isn't always the credentials. In cases I have at work, A
| can't talk to B because of firewalls, so the transfer has to go through
| a 3rd system.
Fair enough.
Sounds like you do need to do two copies.
If you need to do a lot you could do something funky like this:
ssh -R 2222:hostB:22 scp /tmp/file local2222:/tmp/file
where "local2222" is a name in your remote .ssh/config that has a Hostname
of "localhost" and a Port of "2222", thus looping the scp's ssh connection
back through the second ssh's remote port forward and out to hostB.
The data's still flowing from hostA to you to hostB, but there's not
intermediate file involved.
Cheers,
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
The trouble with calling tech support is that you end up talking to someone
whose best career option is to work in tech support
- Lamont Lucas
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
