> Applink is roughly explained at > http://www.openssl.org/support/faq.html#PROG2. The matter was discussed > about half a year ago but no decision was made. See > http://mail.python.org/pipermail/python-dev/2008-March/077424.html > > applink.c is just a table of integer constants to function pointers. It > makes mixing of different CRTs secure. You'll get the idea after reading > the file, Martin. A similar approach could be useful for Python, too. I (now) understand all that. I still don't understand why Python should use it, *for OpenSSL*. (that Python might use something like that for itself is probably not the point Larry is trying to make). Now that I read the archives, I see that I didn't understand in February what specific problem would be solved. I still don't see today how it would solve a problem. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4