Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 24 Feb 2001 19:02:40 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin with sockscap32 Message-ID: <20010224190240.I6893@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200102222041.f1MKfKj29110@quickmonkey.com> <20010224164002.B6385@redhat.com> <200102242149.f1OLns802613@quickmonkey.com> <20010224175137.A6846@redhat.com> <3A9844BC.7485D813@ece.gatech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3A9844BC.7485D813@ece.gatech.edu>; from cwilson@ece.gatech.edu on Sat, Feb 24, 2001 at 06:33:16PM -0500 On Sat, Feb 24, 2001 at 06:33:16PM -0500, Charles S. Wilson wrote: >Chris Faylor wrote: >>However, the only way the problem is going to be narrowed down is if >>you, or someone, debugs sockscap. The sources *must* be available >>given Cygwin's licensing agreement. > >Not really -- see my other message. Sockscap doesn't link or use >cygwin itself -- it modifies the networking layer of the machine on >which it is installed. Actually, that means that on MADHU's machine, >*cygwin* is using *sockscap*, not the other way around. So cygwin's >license doesn't apply. Yeah, your message crossed mine. Thanks for doing the research. I stand corrected. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple