Re: Why GNU GPL is bad for crypto deployment

New Message Reply About this list Date view Thread view Subject view Author view

jwashbur@whittman-hart.com
Fri, 2 Oct 1998 08:54:37 -0500


---------------------- Forwarded by John Washburn/Whittman-Hart LP on
10/02/98 08:55 AM ---------------------------

John Washburn
09/29/98 08:41 AM

To: Adam Back <aba@dcs.ex.ac.uk>
cc:
Subject: Re: Why GNU GPL is bad for crypto deployment (Document link not
      converted)

As the GPL goes, I agree with Adam. I am currently re-writing some code to
specifically remove GNU code "contamination". Those are the exact words
used by my attorney. I had trouble describing to my delightfully mercenary
attorney why the GPL may not be a "Bad Thing" from my perspective.

But Adam's point stands, that the GPL does limits the possibilities of wide
spread distribution through comercial channels. If the goal is wide-spread
use and implementation, commercial channels should not be ignored.

Perhaps the following is an acceptable compromise:
     On Win '95/NT platforms create Dynamic Link Libraries covered by the
GLPL.
     On UNIX platforms create shared library modules covered by the GLPL.

The encapsulation provided by the DLL and shared library, allows for use by
commercial products and only the source code for the library modules need
be re-distributed.

Better is a BSD license with a contribution list from here to the moon.
Legally, this presents far less challenge to deriving commercial products
from our coding project. We could include in the library/libraries a
function, GetContributors(), that returns a pointer to an array of strings
(similar to argv[]) with contributors names.

In Liberty,
John Washburn


New Message Reply About this list Date view Thread view Subject view Author view

 
All trademarks and copyrights are the property of their respective owners.

Other Directory Sites: SeekWonder | Directory Owners Forum

The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:15:19