Serious trouble with https (Python 2.2.3 & 2.3.3), How to check for working ssl?

Andrew MacIntyre andymac at bullseye.apana.org.au
Wed May 19 19:15:39 EDT 2004


On Wed, 19 May 2004, Phillip wrote:

> My strong suspicion is that the socket stuff (dunno exact libname right
> now...) is compiled without ssl support.
>
> What I would like to know now is following:
>
>
> 1) What is the default setting for the compilation of the original
> Python source? _With_or _without_ ssl support?

The ssl support, on both 2.2.x and 2.3.x, is built via the setup.py script
which gets run after the interpreter itself is built.  If setup.py can
find the SSL headers, it will attempt to build with SSL support.

> I just downloaded the sources onto Debian Linux and did the configure,
> make, make install dance. No fumbling on my side done here.
>
> Is there anybody I could ask who could know? Appart from bugging Guido
> van Rossum over this that is. :-)

You didn't inspect the logs from the make process?  the output from
setup.py towards the end will give clues as to whether SSL support was
included.

> 2) If this can't be said for shure _how_ can I find out if my version of
> Python was compiled with ssl support? Apart from trying to connect via
> https that is. Like I said: I've got a seriously growing suspicion that
> it _is_ unsupported ssl due to compilation.

For 2.3.x, there will be a _ssl.so to go with the _socket.so.

There is no visible indication with 2.3.x.

> 3) Where do I change the compile options (???), switches (???) - I don't
> know how excactly this stuff is called - to set such stuff as what
> things are compiled into the installation and which aren't. This is a
> more general Linux/make/configure/gcc/whatnot sort of question, I know,
> but I would be gratefull for any help.

Build options for SSL support are in setup.py.

Linux distros tend to "localise" anything and everything, so its not
possible that setup.py is not finding the SSL headers because they're
not where non-Debian people expect them to be.  Added to the fact that
Linux distros also seem to go overboard in separating "developer" bits
(like header files) from "application bits".  If you need the headers, you
need to install the apropriate developer packages.

I would have expected the Debian package of Python to have SSL support
though, unless its an optional package...

--
Andrew I MacIntyre                     "These thoughts are mine alone..."
E-mail: andymac at bullseye.apana.org.au  (pref) | Snail: PO Box 370
        andymac at pcug.org.au             (alt) |        Belconnen  ACT  2616
Web:    http://www.andymac.org/               |        Australia




More information about the Python-list mailing list