This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dlmiles
Recipients Arfrever, dlmiles, flox, giampaolo.rodola, janssen, jcea, pitrou, vstinner
Date 2010-04-09.06:54:09
SpamBayes Score 1.2942681e-06
Marked as misclassified No
Message-id <1270796053.85.0.939298077881.issue8108@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2010-04-09 06:54:14dlmilessetrecipients: + dlmiles, jcea, janssen, pitrou, vstinner, giampaolo.rodola, Arfrever, flox
2010-04-09 06:54:13dlmilessetmessageid: <1270796053.85.0.939298077881.issue8108@psf.upfronthosting.co.za>
2010-04-09 06:54:12dlmileslinkissue8108 messages
2010-04-09 06:54:11dlmilescreate