Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
From:	Cary Lewis <cslewis AT mobilecom DOT com>
Subject:	Re: OpenSSH on windows Problem
Date:	Thu, 2 Sep 2004 18:31:05 +0000 (UTC)
Lines:	16
Message-ID:	<loom.20040902T202705-585@post.gmane.org>
References:	<BAY9-DAV22djnnWLwf400019998 AT hotmail DOT com>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	main.gmane.org
User-Agent:	Loom/3.14 (http://gmane.org/)
X-Loom-IP:	207.35.217.254 (Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322))
X-IsSubscribed:	yes

From what I understand, simply using cygwin binaries like ssh, perl, bash, etc. 
does not virally infect a propietary system with the GPL.

So, if you plan on using sshd and sftp as part of your commerical app, you don 
not have to license cygwin.

Any changes you make to sshd or sftp would have to be published.

You have to check to make sure that distributing cygwin doesn't run you afoul 
of the GPL.

That being said, I think we should all encourage RedHat to publish cygwin under 
the LGPL to allow cygwin1.dll to be used without virally infecting application 
code. But that is just my opinion.




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -