https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5469
--- Comment #5 from bunzel@xxxxxxxxx 2010-12-07 15:43:31 PST ---
After reviewing TightVNC's source code and further prodding of the user who
experienced the issue, it turned out that the *client* that was used to
generate the invalid VNC traffic was a gtk client using the gtk-vnc library.
It appears that any VNC clients using gtk-vnc before that particular bug was
fixed[1] will exhibit the described protocol violation that prevents wireshark
from dissecting the session.
[1]
http://git.gnome.org/browse/gtk-vnc/commit/?id=bc9e2b19167686dd381a0508af1a5113675d08a2
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
