Added a parameter (server_mode, type int) to the 
newPySSLObject() function. If its value is non-zero, a server 
SSL transaction is attempted - by using SSL_accept() instead 
of SSL_connect().
Also, the parameter has been added to the PySocket_ssl() 
constructor function (it defaults to 0 for compatibility) and 
the ssl() documentation reflects the change.

A new python function has been added (pending(), C function 
PySSL_SSLpending()), which calls SSL_pending() and returns 
its return value as a python integer. Added documentation 
for this one, too.
The return value is the number of bytes still to be read from 
the input buffer, so that if it's greater than zero it is useless 
to call a select() in a nonblocking scenery.

Trivial patch but it's the only way to code an SSL server 
without third-party stuff.

Logged In: YES 
user_id=21627

There's no uploaded file!  You have to check the
checkbox labeled "Check to Upload & Attach File"
when you upload a file. In addition, even if you
*did* check this checkbox, a bug in SourceForge
prevents attaching a file when *creating* an issue.

Please try again.

(This is a SourceForge annoyance that we can do
nothing about. :-( )

Logged In: YES 
user_id=21627

Can you please provide patches for Doc/lib/libsocket.tex as
well?

Contribution of a small example of an SSL server in
Demo/sockets would be appreciated as well. The demo should
ship with a pre-generated self-signed certificate (private
key without pass phrase); comments inside the sslserver.py
should list the openssl commands used to generate the
certificate.

Are you interested in contributing such an example?

I believe issue 1018 renders this one moot.  Though more examples in Demo 
is still a good idea.  I'll contribute a threaded server example for 
that.

I'll take on providing the server example.

I think the example in Lib/test/test_ssl.py will have to suffice.

It would be nice to have an asyncore example server, too.

Marking as out-of-date