https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3070
Stephen Fisher <stephentfisher@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #3 from Stephen Fisher <stephentfisher@xxxxxxxxx> 2008-11-25 17:47:16 PDT ---
I just tested this code with a capture of TightVNC traffic I had laying around
and it threw errors all over the place! :-). I am going to remove the
REPORT_DISSECTOR_BUG() macro call under case TIGHT_AUTH_TYPE_REPLY in
vnc_startup_messages() because it isn't really a dissector bug when it simply
doesn't support a certain type of packet.
Federico - do you know which type of packet comes after a
TIGHT_AUTH_TYPE_REPLY? We need to set per_conversation_info->vnc_next_state to
the next packet type within that case statement so it doesn't get stuck
thinking every packet is a TIGHT_AUTH_TYPE_REPLY. Thanks in advance.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
