Re: v0.16beta1 - win32 no OPENSSL_Applink fatal error
Larry Bugbee <[email protected]>
| Newsgroups | gmane.comp.python.cryptography |
|---|---|
| Message-ID | <[email protected]> |
On Jun 7, 2006, at 5:35 AM, Arno Bakker wrote: > Yes. The only solution I found so far is to recompile python with > the applink.c included. See my earlier mails: > > https://listserv.surfnet.nl/scripts/wa.exe?A2=ind0604&L=python- > crypto&P=1049 It looks to me like we have a problem. Not all apps are going to conveniently remember to call OPENSSL_Applink(), nor in my opinion, should they. Some may not Soooo.... 1- Why does everything work without this stunt under MacOSX? ...or is that a false positive? 2- Is there some way to trick OpenSSL by adding something to __m2crypto.i and __init__.py so that when M2Crypto is imported, OPENSSL_Applink() gets called? (I tried but my knowledge of exactly how is limited.) 3- OPENSSL_Applink(), in applink.c, has a once flag. Do we call it from every load_key() and save_key()? 4- ??? Larry