You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/tiran'closed_at=<Date2017-05-06.00:43:24.956>created_at=<Date2017-05-05.23:38:45.315>labels= ['expert-SSL', 'type-crash']
title='ssl.wrap_ssl will fail on do_handshake if default parameters are supplied by user'updated_at=<Date2017-05-06.00:43:24.946>user='https://github.com/DenSA-Inc'
After a big problem with the newest ejabberd-version and sleekxmpp I located the problem in ssl.wrap_socket. When called with no parameters the later do_handshake (method of ssl.SSLSocket) fails with an exception. When called with keyword-parameters which match the default values (except for do_handshake_on_connect), do_handshake will fail when called after that. Once I have time I will edit this post to add the required information here, but for now I refer to the issue filed on github: fritzy/SleekXMPP#452
The important information is in comments 2 and 3.
I just realised that the server stopped supporting TLS-v1.0 and the code still tried to establish a TLS-v1.0-connection. Yet the server responded with TLS-v1.2. So no bug here.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: