http://bugzilla.novell.com/show_bug.cgi?id=525295 Summary: python: fix potential hang during ssl handshake Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other URL: http://bugs.python.org/issue5103 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: jmatejek@novell.com ReportedBy: vuntz@novell.com QAContact: qa@suse.de Found By: --- As discussed by mail, I'd like to see a fix for http://bugs.python.org/issue5103. Here's the mail I sent: ============================== I'm working on a script to generate the database used on http://tmp.vuntz.net/opensuse-packages/obs.py (this is a page that can be used to see the status of packages in openSUSE compared to upstream). This script needs to checkout a lot of stuff from the build service, and I experience the following bug from time to time (enough for it to be really annoying): http://bugs.python.org/issue5103. The short story is that a connection to a SSL server can hang forever because the socket timeout is ignored. You can see that the code in the 2.6 branch is still the way it's described in the bug: http://svn.python.org/view/python/branches/release26-maint/Lib/ssl.py?view=m... (relevant part of the code is after the "if do_handshake_on_connect:") Interestingly, in the 3.0 and 3.1 branches, things are different: http://svn.python.org/view/python/branches/release30-maint/Lib/ssl.py?view=m... (relevant part of the code is after the "if do_handshake_on_connect:") Note how a timeout that is positive is not ignored. You can see that the patches applied for 2.6 and 3.x are different: http://svn.python.org/view/python/branches/release26-maint/Lib/ssl.py?view=diff&r1=64577&r2=64578 http://svn.python.org/view/python/branches/release30-maint/Lib/ssl.py?r1=59010&r2=59340 Do you think we could adopt the 3.x way in the openSUSE package? (and push the change upstream, of course) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.