[Twisted-Python] Strange SSL behaviour.

Jean-Paul Calderone exarkun at divmod.com
Mon Jun 18 13:33:29 EDT 2007

On Mon, 18 Jun 2007 18:49:26 +0400, Voznesensky Vladimir <vovic at nfi.kiae.ru> wrote:
>Dear all!
>I have a bug demonstration code.
>Blocking SSL works where Twisted one does not.
>It is below.
>How should I handle this case?
>Can anybody tell me what to do with this bug?
>I can dig into twisted sources, but I'm not a
>twisted specialist, so it could take weeks to
>boil them to get the dirt.
>Help me, please.


I took a look at your sample code a few days ago and
nothing struck me as being the cause of this behavior.
I just took another look and it still seems like this
shouldn't be happening, although I noticed a few other
miscellaneous problems with the Twisted client (none
would manifest until it managed to get further than it
does, though).

Next I did a capture with ethereal and I noticed that
the server is actually sending back unencrypted bytes
in response to 0 + _CMD.  It's not clear why it would
reliably do this for the Twisted client and not for the
version which directly uses OpenSSL, unless it is somehow
timing related.

I suppose at this point I'd check into the server's
behavior to verify this observation and try to determine
why it is behaving this way.


More information about the Twisted-Python mailing list