https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5469
--- Comment #4 from bunzel@xxxxxxxxx 2010-12-06 13:48:59 PST ---
The client responsible for this issue appears to be TightVNC. The attached
packet capture was created using TightVNC 1.3.10. I'll also file a bug with
them.
Although I'm honored that you consider checking in my works-for-me patch, I
don't think this is the right way to fix it, since silently accepting a
deviation from the spec is probably not a good idea. In my opinion, it's
missing at least a comment explaining why this is accepted (I've only now found
out which client is responsible) and optionally a tree item in the GUI
indicating the deviation. I'd do the latter myself but I'm afraid I'm not
acquainted enough with wireshark development to do it properly.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.