https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3070
--- Comment #5 from Yaniv Kaul <mykaul@xxxxxxxxx> 2010-11-03 08:58:21 PDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > 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.
>
> I've just filed a bug with a patch to hopefully improve the situation.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5366
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
