[JDEV] license

[Corbett J. Klempay]

The code in question (cryptlib) would be used in both the server and the
client.  The server would make use of mod_digsig to give it support for
dealing with digital signature capable clients...so one would think that
you would want as many as possible (if not all) servers to have this
support enabled, as otherwise their clients cannot make use of their
extended capabilities.  mod_digsig allows clients to securely log on, as
well as for the server to be able to issue digital certificates.  The code
would be used on the client end for signing and verification when dealing
with other clients (and also for securely logging onto the server).  The
license thing could be skirted a bit (as you suggested) if it was just a
separate module that could be downloaded/enabled at will...and clients
will be much this way.  (client authors can choose to make vanilla as well
as authenticated clients available)  *But*, since you'll likely want as
many servers as possible to have it enabled, it's going to be the case
that the license issue will come up with all of the servers running it.

------------------------------------------------------------------------------
Corbett J. Klempay			         Quote of the Week:
http://www.acm.jhu.edu/~cklempay       "A commune is where people join 
					together to share their lack of 
					wealth."
------------------------------------------------------------------------------

On Mon, 26 Apr 1999, Eliot Landrum wrote:

> I'm not really following how this code is going to be fit into the
> project, so if this is irrelevant, please disregard - this is just a
> thought I had. A lot of times if an item cannot be included because of
> specific licensing problems, it is done as a module or patch type of thing
> that can be downloaded seperetly (precompiled or what have you). Would it
> be possible to do that for this?
> 
> Just an idea that popped in my head.. (gosh that happens too much!).
> 
> Eliot Landrum
> elandrum at bigfoot.com
> 
> On Mon, 26 Apr 1999, Corbett J. Klempay wrote:
> 
> > I haven't heard back from Peter Gutmann at all, but I think we cannot put
> > it out under GPL...this is ripped from the header of one of the bigint
> > code files:
> > 
> >  * The licence and distribution terms for any publically available version
> > or
> >  * derivative of this code cannot be changed.  i.e. this code cannot
> > simply be
> >  * copied and put under another distribution licence
> >  * [including the GNU Public Licence.]
> > 
> > So what does this mean for us?  I mean, do we avoid using this if we
> > cannot put it out under GPL?  Or do we use it and put it out under its
> > license? (as in how important is it that we release under GPL)
> > 
> > ------------------------------------------------------------------------------
> > Corbett J. Klempay			         Quote of the Week:
> > http://www.acm.jhu.edu/~cklempay       "A commune is where people join 
> > 					together to share their lack of 
> > 					wealth."
> > ------------------------------------------------------------------------------
> > 
> > 
> > 
>