From owner-freebsd-ports  Sat Aug 24 09:53:42 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA16101
          for ports-outgoing; Sat, 24 Aug 1996 09:53:42 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA16078;
          Sat, 24 Aug 1996 09:53:29 -0700 (PDT)
Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id KAA02442; Sat, 24 Aug 1996 10:53:08 -0600 (MDT)
Message-Id: <199608241653.KAA02442@rover.village.org>
To: Brian Tao <taob@io.org>
Subject: Re: Building SOCKS5 port, linking into ssh 1.2.14 
Cc: Douglas Ambrisko <ambrisko@tcsi.com>,
        FREEBSD-PORTS-L <freebsd-ports@freebsd.org>,
        FREEBSD-CURRENT-L <freebsd-current@freebsd.org>, ylo@cs.hut.fi
In-reply-to: Your message of Thu, 22 Aug 1996 23:29:06 EDT
Date: Sat, 24 Aug 1996 10:53:08 -0600
From: Warner Losh <imp@village.org>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

:     Tatu, perhaps ssh's configure script needs to be updated to use
: --with-socks4 and --with-socks5?

A local user here built ssh with socks 5 support.  The socks support
in 1.2.14 at least was socks 4.  He was able to just include the right
thing that did the right #define magic for things like connect, etc.
He claimed that hacking the headers and *NOT* configuring for socks
made this just work.

I'll see if I can get him to generate some patches and I'll pass them
along (if he hasn't already sent them directly to the ssh mailing
list).

Changing everything to SOCKSxxxx is definitely a big pain and not the
right way to fix this problem. :-(

Warner