Certificate Management stuff

[Robert Olson]

yes, I added those to the stock pyopenssl.

No code is needed to extend pyopenssl, all I need is now in there. 
m2crypto would need the things I enumerated earlier. 

--bob

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

> 
> Is this based on the current release or an older one? If I'm not mistaken,
> the extensions and attributes are something you just added to our pyopenssl,
> so standard pyopenssl is missing them too, right?
> 
> It might be clearer if you show what stock pyopenssl has that m2crypto
> doesn't that we are using.
> 
> What I'm trying to quantify is the amount of code is needed to extend
> pyopenssl vs the amount needed to extend m2crypto and once that's
> understood, how much is done for each. Then it's much easier to have a clear
> conversation about the trade-offs of each solution and the work involved.
> 
> --Ivan 
> 
> > -----Original Message-----
> > From: Robert Olson [mailto:olson at mcs.anl.gov] 
> > Sent: Wednesday, January 28, 2004 4:05 PM
> > To: judson at mcs.anl.gov; 'Keith Jackson'
> > Cc: 'AG Dev'; 'Matt Rodriguez'
> > Subject: RE: Certificate Management stuff
> > 
> > 
> > >Being so core to our toolkit, it significanly limits the 
> > >distributability of our code. M2Crypto is the standard SSL 
> > solution for 
> > >SOAPpy and WSTools, most likely ZSI as well, so I'm 
> > interested in if it 
> > >has the interfaces we care about.
> > 
> > It is missing many of the pieces that I need (detailed 
> > manipulation of names,  no support for extensions or attributes).
> > 
> > -bob 
> > 
> > 
> 
>