wasm-demo/demo/ermis-f/python_m/cur/0324

49 lines
2.1 KiB
Plaintext

From: mal at lemburg.com (M.-A. Lemburg)
Date: Fri, 9 Apr 1999 15:53:57 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> <370E3C56.D035A3FB@lockstar.com>
Message-ID: <370E2295.31A119F0@lemburg.com>
Content-Length: 1535
X-UID: 324
Mordy Ovits wrote:
>
> M.-A. Lemburg wrote:
> >
> >>I have a fairly complete SWIGing of OpenSSL/SSleay working. I made it on
> >>company time, so I have to get company permission to release it. If there is
> >>real interest, I'll push for us to release it. It does all the X.509 stuff, is
> > > very OO, and builds on win32 and unices.
> > > Interested?
> >
> > 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.\
>
> That's debatable. The SWIG bindings contain no crypto code in their own right.
> It is merely glue to crypto code. I wouldn't be able to release statically
> prebuilt libraries, but why would I want to anyway? Our lawyers keep waffling
> on this, which is why I haven't released it already. I'm really pleased with
> it, and would love give something back to the Python community. <SIGH> How
> long before we Americans are reduced to doing Crypto with a deck of cards? (See
> Bruce Schneier's Solitaire).
Well, the NCSA folks did something similar in their WWW server (they
included bindings to some crypto-lib for authentication) and
were called back by the NSA... but maybe the situation is different
now.
--
Marc-Andre Lemburg Y2000: 266 days left
---------------------------------------------------------------------
: Python Pages >>> http://starship.skyport.net/~lemburg/ :
---------------------------------------------------------