From owner-freebsd-questions@FreeBSD.ORG Thu May 8 22:42:47 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 284BE106564A for ; Thu, 8 May 2008 22:42:47 +0000 (UTC) (envelope-from unix@devil.mutu.us) Received: from devil.mutu.us (devil.mutu.us [206.229.45.53]) by mx1.freebsd.org (Postfix) with ESMTP id E908F8FC0C for ; Thu, 8 May 2008 22:42:46 +0000 (UTC) (envelope-from unix@devil.mutu.us) Received: from devil.mutu.us (localhost [127.0.0.1]) by devil.mutu.us (8.13.8/8.13.8) with ESMTP id m48Mgf1e000932 for ; Thu, 8 May 2008 17:42:46 -0500 (CDT) (envelope-from unix@devil.mutu.us) Received: (from unix@localhost) by devil.mutu.us (8.13.8/8.13.8/Submit) id m48Mga9v000931 for freebsd-questions@freebsd.org; Thu, 8 May 2008 17:42:36 -0500 (CDT) (envelope-from unix) Date: Thu, 8 May 2008 17:42:35 -0500 From: Valeriu Mutu To: freebsd-questions@freebsd.org Message-ID: <20080508224235.GA87584@devil.mutu.us> Mail-Followup-To: freebsd-questions@freebsd.org References: <200805060931.18936.beech@freebsd.org> <20080506173912.GB85015@Grumpy.DynDNS.org> <200805060959.28509.beech@freebsd.org> <48229099.5030004@boosten.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48229099.5030004@boosten.org> Organization: Mutu User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: [SSHd] Increasing wait time? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2008 22:42:47 -0000 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. > -- > http://www.boosten.org > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- Valeriu Mutu