Date: Fri, 09 May 2008 05:01:15 +0200 From: Peter Boosten <peter@boosten.org> To: freebsd-questions@freebsd.org Subject: Re: [SSHd] Increasing wait time? Message-ID: <4823BE7B.2050806@boosten.org> In-Reply-To: <20080508224235.GA87584@devil.mutu.us> References: <q7412457qoumm8v8dbth10fug2ctbrlfp0@4ax.com> <200805060931.18936.beech@freebsd.org> <20080506173912.GB85015@Grumpy.DynDNS.org> <200805060959.28509.beech@freebsd.org> <p05200f04c4482c6bafb9@[192.168.2.250]> <48229099.5030004@boosten.org> <20080508224235.GA87584@devil.mutu.us>
next in thread | previous in thread | raw e-mail | index | archive | help
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? >> >> Peter > > Exactly. > > 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 userA@machineA "ssh -f -L localhost:4444:localhost:22 userB@machineB 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 user@your.friends.host and then open a new shell: scp -P 4444 the-file-you-want-to-copy user@localhost: This works easiest with agent forwarding, but I guess any authentication will do. Peter -- http://www.boosten.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4823BE7B.2050806>