Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem
======================
Having a server with SSLSocket waiting for connections, the incoming connection, failed on automatic do_handshake(), stays open forever — accept() raises the SSLError and does not return client connection socket.
How reproducible
================
146%
Steps to reproduce
==================
server side:
1. create a SOCK_STREAM socket
2. wrap it with wrap_socket()
3. listen()
4. accept()
client side:
1. telnet to this port
2. enter any random text
Expected results
================
1. Incoming connection is closed and client disconnected
Actual results
==============
1. On the server side, due to exception, the reference to the incoming connection gets lost.
2. The client stays connected as long as the server operates.
Actually, this issue can lead to unintentional DoS, if a client will try open new connections on a failure — without explicit closing failed ones.
Possible fix
============
Add into do_handshake() something like that:
try:
self._sslobj.do_handshake()
except SSLError as e:
self._sock.close()
raise e
Additional info
===============
Python bugzilla issue: http://bugs.python.org/issue17918
Important: only Python2 versions are affected. Python3 works OK.
Possibly related issue: http://bugs.python.org/issue12378 (differs: see the line above)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-1582.html
Description of problem ====================== Having a server with SSLSocket waiting for connections, the incoming connection, failed on automatic do_handshake(), stays open forever — accept() raises the SSLError and does not return client connection socket. How reproducible ================ 146% Steps to reproduce ================== server side: 1. create a SOCK_STREAM socket 2. wrap it with wrap_socket() 3. listen() 4. accept() client side: 1. telnet to this port 2. enter any random text Expected results ================ 1. Incoming connection is closed and client disconnected Actual results ============== 1. On the server side, due to exception, the reference to the incoming connection gets lost. 2. The client stays connected as long as the server operates. Actually, this issue can lead to unintentional DoS, if a client will try open new connections on a failure — without explicit closing failed ones. Possible fix ============ Add into do_handshake() something like that: try: self._sslobj.do_handshake() except SSLError as e: self._sock.close() raise e Additional info =============== Python bugzilla issue: http://bugs.python.org/issue17918 Important: only Python2 versions are affected. Python3 works OK. Possibly related issue: http://bugs.python.org/issue12378 (differs: see the line above)