https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2800
Summary: "Response flags" in GIOP Request is misinterpreted
Product: Wireshark
Version: 1.0.2
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: wireshark@xxxxxxxxxx
Build Information:
Version 1.0.2 (SVN Rev 25698)
Copyright 1998-2008 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.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Recent GIOP specs have 4 SYNC policies: NONE(0), WITH_TRANSPORT(1),
WITH_SERVER(2), and WITH_TARGET(3). The GIOP Request dissector is assuming
that response_flags is equal to the value of the SYNC policy, but it's not.
Quoting:
response_flags is set to 0x0 for a SyncScope of NONE and WITH_TRANSPORT. The
flag is set to 0x1 for a SyncScope of WITH_SERVER. A non exception reply to a
request message containing a response_flags value of 0x1 should contain an
empty body, i.e. the equivalent of a void operation with no out/inout
parameters. The flag is set to 0x3 for a SyncScope of WITH_TARGET. These values
ensure interworking compatibility between this and previous versions of GIOP.
This is apparently a longstanding bug. I found this message from 2003:
http://ethereal.netmirror.org/lists/ethereal-users/200303/msg00135.html
that describes this bug.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
