Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] [PATCH] RFC: Handling and reassembling TCP Out-Of-Order pack

From: "Fernandez, Rafael" <Rafael.Fernandez@xxxxxxxxxxxxxxxx>
Date: Tue, 7 Jun 2011 15:59:36 -0500
Which release may I apply this patch to?
Rafael

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Max Dmitrichenko
Sent: Sunday, May 29, 2011 7:28 PM
To: Developer support list for Wireshark
Subject: [Wireshark-dev] [PATCH] RFC: Handling and reassembling TCP Out-Of-Order packets

Hi!

I've just submitted a patch [1] to the bugzilla and wish to discuss it here.

The patch was born after the discussion [2] happened about a month
ago. There we came to the conclusion that everything works fine until
application level PDU is fragmented and the first fragment is lost and
retransmitted later. This situation is extremely painful for the
protocols which use encryption, because it breaks everything.

I tried to implement it without changing the current behavior for
dissectors which are unaware of this feature.

I guess such a core change won't go to the upcoming 1.6.0, but I would
be happy to see it in the 1.7.0 or may be
in 1.6.1 - you decide.

[1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5971
[2] http://www.wireshark.org/lists/wireshark-dev/201105/msg00039.html

--
Max
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe


CONFIDENTIALITY AND SECURITY NOTICE

The contents of this message and any attachments may be confidential and proprietary and also may be covered by the Electronic Communications Privacy Act. This message is not intended to be used by, and should not be relied upon in any way, by any third party.  If you are not an intended recipient, please inform the sender of the transmission error and delete this message immediately without reading, disseminating, distributing or copying the contents. Citadel makes no assurances that this e-mail and any attachments are free of viruses and other harmful code.