Certificate Management stuff

[Robert Olson]

It'd be interseting to see the MSR lawyers' justification for why they 
can't look at LGPL code.

If you want to spearhead an effort bring m2crypto up to speed, that's fine 
with me; I can supply test code for the various bits of pyopenssl that I 
use, but will forge ahead using the tools that work now.

--bob

On Wed, 28 Jan 2004, Ivan R. Judson wrote:

> 
> It's evident that M2Crypto support could be integrated with pyGlobus and be
> supported by Matt, pyOpenSSL can't. We've had a lot of feedback that us
> being bsd based and working to only include bsd licensed code is what the
> community wants. I have not done a survey that asks why people who are not
> using the agtk are not using it, indeed it's hard to tell who they are :-).
> 
> --Ivan
> 
> PS - We do know that MSR (ie, Jay, et al) can't even look at the code if
> it's even LGPL, which does inhibit our ability to collaborate with them. I
> don't know if this is the policy for other commercial software vendors.
> 
> > -----Original Message-----
> > From: Robert Olson [mailto:olson at mcs.anl.gov] 
> > Sent: Wednesday, January 28, 2004 4:06 PM
> > To: judson at mcs.anl.gov
> > Cc: 'AG Dev'
> > Subject: RE: Certificate Management stuff
> > 
> > At 03:38 PM 1/28/2004, Ivan R. Judson wrote:
> > >it significanly limits the distributability of our code.
> > 
> > Is this theoretical or have we had people who couldn't use 
> > AGTk due to LGPL components? 
> > 
> > 
> 
>