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:
When gnutls receives multiple (e.g. 32) KeyUpdate messages on a connection, it closes the connection
Version-Release number of selected component (if applicable):
gnutls-3.6.5-2.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. run test-tls13-keyupdate.py from tlsfuzzer
2.
3.
Actual results:
multiple KeyUpdate messages ...
Error encountered while processing node <tlsfuzzer.messages.KeyUpdateGenerator object at 0x7f7534ebc828> (child: <tlsfuzzer.messages.KeyUpdateGenerator object at 0x7f7534ebc860>) with last message being: <tlslite.messages.KeyUpdate object at 0x7f753299f518>
Error while processing
Traceback (most recent call last):
File "/root/tlsfuzzer/tlsfuzzer/runner.py", line 234, in run
self.state.msg_sock.sendMessageBlocking(msg)
File "/root/tlsfuzzer/tlslite/messagesocket.py", line 186, in sendMessageBlocking
for _ in self.sendMessage(msg):
File "/root/tlsfuzzer/tlslite/messagesocket.py", line 181, in sendMessage
for res in self.flush():
File "/root/tlsfuzzer/tlslite/messagesocket.py", line 121, in flush
for res in self.sendRecord(msg):
File "/root/tlsfuzzer/tlslite/recordlayer.py", line 630, in sendRecord
for result in self._recordSocket.send(encryptedMessage, padding):
File "/root/tlsfuzzer/tlslite/recordlayer.py", line 103, in send
for result in self._sockSendAll(data):
File "/root/tlsfuzzer/tlslite/recordlayer.py", line 69, in _sockSendAll
bytesSent = self.sock.send(data)
File "/root/tlsfuzzer/tlslite/bufferedsocket.py", line 34, in send
return self.socket.send(data)
BrokenPipeError: [Errno 32] Broken pipe
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "scripts/test-tls13-keyupdate.py", line 575, in main
runner.run()
File "/root/tlsfuzzer/tlsfuzzer/runner.py", line 248, in run
raise AssertionError("Unexpected closure from peer")
AssertionError: Unexpected closure from peer
Expected results:
OK
Additional info:
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.
https://access.redhat.com/errata/RHSA-2019:3600
Description of problem: When gnutls receives multiple (e.g. 32) KeyUpdate messages on a connection, it closes the connection Version-Release number of selected component (if applicable): gnutls-3.6.5-2.el8.x86_64 How reproducible: always Steps to Reproduce: 1. run test-tls13-keyupdate.py from tlsfuzzer 2. 3. Actual results: multiple KeyUpdate messages ... Error encountered while processing node <tlsfuzzer.messages.KeyUpdateGenerator object at 0x7f7534ebc828> (child: <tlsfuzzer.messages.KeyUpdateGenerator object at 0x7f7534ebc860>) with last message being: <tlslite.messages.KeyUpdate object at 0x7f753299f518> Error while processing Traceback (most recent call last): File "/root/tlsfuzzer/tlsfuzzer/runner.py", line 234, in run self.state.msg_sock.sendMessageBlocking(msg) File "/root/tlsfuzzer/tlslite/messagesocket.py", line 186, in sendMessageBlocking for _ in self.sendMessage(msg): File "/root/tlsfuzzer/tlslite/messagesocket.py", line 181, in sendMessage for res in self.flush(): File "/root/tlsfuzzer/tlslite/messagesocket.py", line 121, in flush for res in self.sendRecord(msg): File "/root/tlsfuzzer/tlslite/recordlayer.py", line 630, in sendRecord for result in self._recordSocket.send(encryptedMessage, padding): File "/root/tlsfuzzer/tlslite/recordlayer.py", line 103, in send for result in self._sockSendAll(data): File "/root/tlsfuzzer/tlslite/recordlayer.py", line 69, in _sockSendAll bytesSent = self.sock.send(data) File "/root/tlsfuzzer/tlslite/bufferedsocket.py", line 34, in send return self.socket.send(data) BrokenPipeError: [Errno 32] Broken pipe During handling of the above exception, another exception occurred: Traceback (most recent call last): File "scripts/test-tls13-keyupdate.py", line 575, in main runner.run() File "/root/tlsfuzzer/tlsfuzzer/runner.py", line 248, in run raise AssertionError("Unexpected closure from peer") AssertionError: Unexpected closure from peer Expected results: OK Additional info: