aboutsummaryrefslogtreecommitdiffstats
path: root/macosx-support-lib-patches
diff options
context:
space:
mode:
authorJohn Thacker <johnthacker@gmail.com>2022-09-11 10:40:25 -0400
committerA Wireshark GitLab Utility <gerald+gitlab-utility@wireshark.org>2022-09-13 23:45:01 +0000
commit56ea9816d9bb439e62eb77fa20e7220783404b83 (patch)
treea71f1f9456c77a51141c16357d7a41295b08dba8 /macosx-support-lib-patches
parent8724c249e1cd2a91e726a682d85924a58ae10b18 (diff)
tcp: Create new conversations on a SYN after a RST or FIN
If we get a SYN packet with the same sequence number as the current conversation, but after a RST (or FIN) segment, create a new conversation. In such a case, this is probably a peer using the same sequence number to retry a handshake that failed with a RST due to a half-open connection. The RST (or ACK that caused a RST) would have an out-of-window sequence number (or inapplicable ACK for the rest of the conversation), which can disrupt the follow info, sequence analysis, desegmentation, etc. unless we create a new conversation. It could also, less likely, be a new connection after a connection close that happened to reuse the same sequence number, in which case we also want to clear out our conversation state. If we haven't received a RST (or FIN), then consider it a retransmission. Fix #18333 (also handles the cases of #16944 and #17616 more smoothly).
Diffstat (limited to 'macosx-support-lib-patches')
0 files changed, 0 insertions, 0 deletions