Wireshark-bugs: [Wireshark-bugs] [Bug 1212] New: Follow SSL Stream gets direction wrong if start

Date: Wed, 8 Nov 2006 22:39:13 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1212

           Summary: Follow SSL Stream gets direction wrong if started from a
                    server->client frame
           Product: Wireshark
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: stephentfisher@xxxxxxxxx


Build Information:
wireshark 0.99.5 (SVN Rev 19866)

Copyright 1998-2006 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.8.20, with GLib 2.10.3, with libpcap 0.9.1, with libz
1.2.2, with libpcre 6.7, with Net-SNMP 5.2.3, with ADNS, without Lua, with
GnuTLS 1.2.11, with Gcrypt 1.2.2, with Heimdal Kerberos, without PortAudio,
without AirPcap.

Running on FreeBSD 6.1-RELEASE-p10, with libpcap version 0.9.1.

Built using gcc 3.4.4 [FreeBSD] 20050518.
--
The "Follow SSL Stream" feature has a similar problem as "Follow TCP Stream"
does as noted in bug #1138.  The problem is when you click on a server->client
packet and do Follow SSL Stream, the hostname/ports in the drop-down list are
reversed from what is actually displayed above.  For example, if you choose the
client->server entry, it shows you server->client traffic.  If you started with
a client->server packet, then these entries work correctly.

The code that displays the drop-down for Follow SSL Stream is similar to that
of Follow TCP Stream, but it doesn't appear to be using a follow file so it
cannot be fixed in the same way (with a patch I submitted to the -dev list
recently).


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.