Re: tmda-ofmipd: V2: Internal support for SSL via tlslite package
Stephen Warren <[email protected]> Wed, 28 Feb 2007 23:22:03 -0700
| Newsgroups | gmane.mail.spam.tmda.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason R. Mastaler wrote: > "Jason R. Mastaler" <[email protected]> writes: > >> Then I tried Evolution, and couldn't get TLS or SSL to work, with either >> version of Python. But the error tmda-ofmipd gave was different: >> >> Incoming connection from: ('127.0.0.1', 56647) >> Incoming connection to: ('127.0.0.1', 8025) >> SENDING SIGN ON MSG >> Data: 'EHLO [127.0.0.1]' >> Data: 'STARTTLS' >> error: uncaptured python exception, closing channel >> <__main__.SMTPSession connected 127.0.0.1:56647 at 0x2b3f331e0950> >> (tlslite.errors.TLSLocalAlert:handshake_failure [asyncore.py|read|69] >> [asyncore.py|handle_read_event|391] [bin/tmda-ofmipd|handle_read|457] >> [/usr/lib/python2.4/site-packages/tlslite/integration/AsyncStateMachine.py|inReadEvent|123] >> [/usr/lib/python2.4/site-packages/tlslite/integration/AsyncStateMachine.py|_doHandshakeOp|157] >> [/usr/lib/python2.4/site-packages/tlslite/TLSConnection.py|handshakeServerAsync|1032] >> [/usr/lib/python2.4/site-packages/tlslite/TLSConnection.py|_handshakeWrapperAsync|1537] >> [/usr/lib/python2.4/site-packages/tlslite/TLSConnection.py|_handshakeServerAsyncHelper|1128] >> [/usr/lib/python2.4/site-packages/tlslite/TLSRecordLayer.py|_sendError|450]) > > I don't know what to make of this. Evolution might be buggy, as other > Linux MUAs seem to work fine with the same code on the same > machine. Perhaps disregard it for now. Very odd, since my copy of evolution links against OpenSSL just like everything else. Anyway, I have reproduced the Evolution error on my system, so I can debug that sometime. I haven't managed to reproduce the flakey SSL problems yet. Looking at the code, it seems what is happening is that tlslite detects some form of error, and closes the SSL session. The code checks for this when writes are attempted later, and throws the exception you're seeing in SSL mode. Since it's pretty easy for you to reproduce, I guess the best thing is for me to come up with a patched tlslite that includes a bunch of extra debug traces, so we can see what kind of error is triggering this whole chain of events, and for you to run that. I guess I should buy a Mac;-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5nELhk3bo0lNTrURAugCAKDY/wE+f4xMmQn1eoEYL0N+jdIfigCg88UX orpQsm6wL6U60ehRRgmREYo= =mu/C -----END PGP SIGNATURE-----