[issue30288] ssl.wrap_ssl will fail on do_handshake if default parameters are supplied by user

[DenSA-Inc]

New submission from 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: 
https://github.com/fritzy/SleekXMPP/issues/452
The important information is in comments 2 and 3.

--
assignee: christian.heimes
components: SSL
messages: 293146
nosy: botter, christian.heimes
priority: normal
severity: normal
status: open
title: ssl.wrap_ssl will fail on do_handshake if default parameters are 
supplied by user
type: crash
versions: Python 3.4

___
Python tracker 
<http://bugs.python.org/issue30288>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30288] ssl.wrap_ssl will fail on do_handshake if default parameters are supplied by user

[DenSA-Inc]

DenSA-Inc added the comment:

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.

--
stage:  -> resolved
status: open -> closed

___
Python tracker 
<http://bugs.python.org/issue30288>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com