From owner-freebsd-current Thu Aug 22 20:29:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA24312 for current-outgoing; Thu, 22 Aug 1996 20:29:15 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA24306; Thu, 22 Aug 1996 20:29:12 -0700 (PDT) Received: from zot.io.org (taob@zot.io.org [198.133.36.82]) by post.io.org (8.7.5/8.7.3) with SMTP id XAA29506; Thu, 22 Aug 1996 23:29:06 -0400 (EDT) Date: Thu, 22 Aug 1996 23:29:06 -0400 (EDT) From: Brian Tao To: Douglas Ambrisko cc: FREEBSD-PORTS-L , FREEBSD-CURRENT-L , ylo@cs.hut.fi Subject: Re: Building SOCKS5 port, linking into ssh 1.2.14 In-Reply-To: <199608221826.LAA11282@cozumel.tcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 22 Aug 1996, Douglas Ambrisko wrote: > > Okay, the big change from Socks 4 to 5 was the change of the > libsocks.a to libsocks5.a and the proxy functions of R to > SOCKS. Yep, replacing all the R*() calls with SOCKS*() calls (including the one in the configure script) did the trick. Outbound ssh now works quite nicely through our firewall. :) The stupid thing is, I remember seeing "SOCKSconnect()" when I was off chasing another problem, and it didn't occur to me later that the fix would be this simple. :-/ Thanks, Doug. Tatu, perhaps ssh's configure script needs to be updated to use --with-socks4 and --with-socks5? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"