From: mal at lemburg.com (M.-A. Lemburg)
Date: Thu, 8 Apr 1999 19:26:52 GMT
Subject: OpenSSL/X.509
References: <7e1hiq$a71$1@Starbase.NeoSoft.COM>
		<7ear25$ksf$1@news-sj-3.cisco.com>
		<14089.11820.416453.80124@bitdiddle.cnri.reston.va.us>
		<3709C8BE.4257C9F1@lemburg.com>
		<14090.16807.950025.496495@bitdiddle.cnri.reston.va.us>
		<370A78B6.2C18D10F@lockstar.com>
		<370BE48E.2BA9750C@lemburg.com> <14092.42263.897530.425040@amarok.cnri.reston.va.us>
Message-ID: <370D02FC.5FA7D302@lemburg.com>
Content-Length: 1095
X-UID: 496                                                  

Andrew M. Kuchling wrote:
> 
> M.-A. Lemburg writes:
> >Sure, but if your company is US based, then chances are high
> >you won't be able to share the code outside the US... that's
> >why I started mxCrypto, BTW.
> 
>         Note that Pat Knight has a UK-based project to SWIG SSLeay;
> could you work using that as a base?  http://www.ktgroup.co.uk/~pat/

I've looked at that code before I started off into mxCrypto. Pat's
approach uses pointers in the internal OpenSSL's data structure
as basis for doing the wrapping. Unfortunately, those pointers
seem to not work properly anymore in more recent versions of OpenSSL.

Also, he swigged the BIO and SSL parts in OpenSSL, mxCrypto takes
care of most of the crypto routines. X.509 and ASN.1 are not
handled in Pat's version.

Thanks for the tip anyway :-)

-- 
Marc-Andre Lemburg                               Y2000: 267 days left
---------------------------------------------------------------------
          : Python Pages >>> http://starship.skyport.net/~lemburg/  :
           ---------------------------------------------------------





