From owner-freebsd-hackers Thu Dec 12 14:24:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12122 for hackers-outgoing; Thu, 12 Dec 1996 14:24:58 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA12117 for ; Thu, 12 Dec 1996 14:24:52 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id OAA01655; Thu, 12 Dec 1996 14:24:47 -0800 (PST) Message-Id: <199612122224.OAA01655@austin.polstra.com> To: roberto@eurocontrol.fr Cc: hackers@freebsd.org Subject: Re: Fwd: CVSup with SSH In-reply-to: <199612121657.IAA17705@austin.polstra.com> References: <199612121657.IAA17705@austin.polstra.com> Date: Thu, 12 Dec 1996 14:24:38 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Following up once more on using the TCP forwarding of ssh to CVSup through a firewall: > * Invoke ssh with: > > -L 5999:localhost:5999 -R 6666:localhost:6666 > ^^^^...........^^^^ (any free port) > > Note that it's "-L" in the first one and "-R" in the second one. > > * Specify "host=localhost" in your cvsupfile. > > * Invoke cvsup with "-P 6666". I tried a large update (src + ports from several days ago) using this method, and it worked great! I am still astounded. Finally there's a proxy that does what it is supposed to do, and does it right. This should be _really_ useful to those poor souls who haven't been able to get the SOCKS stuff working. I'm going to document it in the manual page and/or the FAQ. (What FAQ?! you ask. I'm workin' on it. ;-) Thanks for this great suggestion! John PS - For best results, disable CVSup's compression (add "-Z" to the command line). Since ssh already compresses, doing it again in CVSup is just a waste of CPU time. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth