From owner-cvs-ports Mon Aug 11 21:13:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26522 for cvs-ports-outgoing; Mon, 11 Aug 1997 21:13:12 -0700 (PDT) Received: from precipice.shockwave.com (ppp-206-170-5-86.rdcy01.pacbell.net [206.170.5.86]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26514; Mon, 11 Aug 1997 21:13:06 -0700 (PDT) Received: from shockwave.com (localhost [127.0.0.1]) by precipice.shockwave.com (8.8.6/8.7.3) with ESMTP id VAA02736; Mon, 11 Aug 1997 21:11:23 -0700 (PDT) Message-Id: <199708120411.VAA02736@precipice.shockwave.com> To: obrien@NUXI.COM cc: Satoshi Asami , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/security Makefile In-reply-to: Your message of "Sun, 10 Aug 1997 22:44:42 PDT." <19970810224442.48530@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Aug 1997 21:11:23 -0700 From: Paul Traina Sender: owner-cvs-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I don't understand why we have a socks4 port at all. socks5 is upwards > > and backwards compatible with 4, and supports a lot more functionality. > > Give me a working socks5 configuration file that works at HP and I'll be > *more* than glad to remove it. HP uses a modified version of socks4, and > I don't know of any of the Linux weenies there that gotten socks5 to work > with the firewall. (I'll be the first to admit, I don't know much about > socks). I don't see what the problem is. They use identical technology and a socks5 server will gladly server socks4 clients, and I believe socks5 clients can use socks4 servers (though I'm not positive). > > > However, socks is much more general than just security, and as such, that's > > Really? I've only ever heard it come up in firewall/security situations. Oh well, so some folks don't have a lot of imagination. :-)