Wierd M2Crypto bug - phony "peer did not return certificate" error

[Heikki Toivonen]

John Nagle wrote:
> I have a little test case for M2Crypto, which just opens up SSL
> connections to
> web servers and reads their certificates.  This works fine.
> 
> But if I execute
> 
>     socket.setdefaulttimeout(5.0)

Yup, this is a known problem, this breaks all M2Crypto code that uses
sockets. The Twisted wrapper part still works, as it hands the network
activity to Twisted.

If you can make do without setdefaulttimeout you should be fine.

This is bug https://bugzilla.osafoundation.org/show_bug.cgi?id=2341

The bug has a patch that works on Linux, but it would need Windows and
Mac specific parts before it can be checked in.

-- 
  Heikki Toivonen