[Dshield] Remote incident handling tool
markt442 at yahoo.com
Fri Dec 2 15:48:31 GMT 2005
Correct. I didn't have much time to review "how" GPL
I've seen more than a few companies modify GPL code,
not publish the source, and then try to make a
commercial go at it.
Bad Mark for not making that point clear!
From: Valdis.Kletnieks at vt.edu
Subject: Re: [Dshield] Remote incident handling tool
Date: Thu, 01 Dec 2005 12:27:52 -0500
To: "General DShield Discussion List"
<list at lists.dshield.org>
On Thu, 01 Dec 2005 04:04:14 PST, Mark said:
> If this is a "for profit" effort, you may want to
> check the license on the distros before going
> - e.g. GPL. If the distro is released under GPL you
> may want to take a hard look at how it would be
Actually, the GPL doesn't care *how* a GPL'ed package
"Activities other than copying, distribution and
modification are not covered by this License; they are
outside its scope. The act of running the Program is
not restricted, and the output from the Program is
covered only if its contents constitute a work based
on the Program (independent of having been made by
running the Program). Whether that is true depends on
what the Program does."
(the part about "work based on the program" is
intended for programs like bison/yacc, where the
program generates code that is itself a derivative
work, since it needs the program libraries in order to
The GPL only matters when you start making *copies*
and distributing them. Andeven *there*, if you're
using the program unmodified, all you need to do
isremember "grab the source when you grab the binary,
and pass along both sourceand binary". If you
modified it, you pass along the binary and the source
*as you modified it*. The only way to actually get
yourself into trouble is to use GPL source in your
product, and then refuse to ship the required sources
on request (you don't even have to ship it *with* the
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
More information about the list