Darryl Miles <[email protected]> added the comment:
In order to build Python with a specific version of OpenSSL followed the CYGWIN
instructions and edited Modules/Setup to make it read (note - I added
"-L$(SSL)" into the linker options too, since by default on CentOS 5.4 i386
OpenSSL build in static library mode ala ../openssl-1.0.0/libssl.a) :
SSL=../openssl-1.0.0
_ssl _ssl.c \
-DUSE_SSL -I$(SSL)/include -I$(SSL)/include/openssl \
-L$(SSL)/lib -L$(SSL) -lssl -lcrypto
It is not clear to me what Python's goals are:
* To be backward compatible, in which case I don't know your historical use of
SSL_shutdown().
* To be a thin-layer (1:1) over OpenSSL, so that "power users" can harness the
full potential of OpenSSL if they are willing to understand the finer points.
* To provide a full-featured Python API.
* To provide a Python API that is easy to use within the Python paradigm.
These goals may not be convergent.
----------
nosy: +dlmiles
Added file: http://bugs.python.org/file16838/python_ssl.c.txt
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue8108>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
