Certificate Management stuff

[Ivan R. Judson]

Understood. We should figure out what if any solution we have to move ahead.

Bob, do you have a set of interfaces that you use to access certificate
information from python? Is that list of interfaces sufficient if supplied
to you?

I'd really like to see a list objects/methods that we use pyopenssl for, Bob
can you produce one for the rest of us? A current comparison to M2Crypto
it's bsd and generated with SWIG) would be helpful too, but we can probably
each do that just as fast at our own pace.

--Ivan 

> -----Original Message-----
> From: Keith Jackson [mailto:krjackson at lbl.gov] 
> Sent: Wednesday, January 28, 2004 2:50 PM
> To: judson at mcs.anl.gov
> Cc: 'Robert Olson'; 'AG Dev'; Matt Rodriguez
> Subject: Re: Certificate Management stuff
> 
> i won't allow code that is tainted with the LGPL go into pyGlobus. 
> Sorry, but that's it. i thought this was code you wrote that 
> used pyOpenSSL. We can't have pyOpenSSL derived code in 
> pyGlobus. That would be a license nightmare.
> --keith
> 
> 
> On Jan 28, 2004, at 9:58 AM, Ivan R. Judson wrote:
> 
> > I agree with the pyOpenSSL strategy and think that's what 
> I've asked 
> > matt to do, effectively, although LGPL will taint their 
> licensing and 
> > I'm sure Keith will have strong objections to a wholesale 
> import if it 
> > taints the code.
> >
> > I've cc'd matt and keith so they can give us input.
> 
>