From owner-freebsd-security Wed Mar 18 11:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10141 for freebsd-security-outgoing; Wed, 18 Mar 1998 11:51:47 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10129 for ; Wed, 18 Mar 1998 11:51:39 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id OAA14051 for ; Wed, 18 Mar 1998 14:48:41 -0500 (EST) Date: Wed, 18 Mar 1998 14:51:34 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-security@FreeBSD.ORG Subject: I need some proxies! :) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk I hate anti-commercial licenses :) I'm about to build a security/internet connection for a local corp. That goes a little something like this: Internet--->IPFW/NAT server--->proxy server/SKIP--->Internal lan. Everything is just peachy till I hat the freakin proxy server. My choice is FWTK proxies or SOCKS. And im not sure if there unable to be used because it's for a commercial entity or not. The license for FWTK to *ME* reads that it can be used even commercial as long as its not used by a commercial entity to make a product. I.e. in this instance to just run internally to the corp. and thats all. But im not positive im checking on this. So my problem comes if I can't use the FWTK proxies since its for a commercial use. What other choices for proxies do i have for a FreeBSD box? who out there is using or has found a good proxy solution to get around this blasted commercial license problem. Don't get me wrong im not pissing and moaning because they don't want it used for free in a commercial environment, im pissing and moaning because they wont port their commercial firewall to FreeBSD. so i get wedged between not using the free one for commercial use and them pretty much refusing to port their commercial product to fbsd. There trying to have their cake and eat it to in my opinion and that sucks. So my snafu right now is trying to find a solution for proxies. ANY ideas anyone has or any pointers would really be appreciated! Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.5 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message