Wireshark-bugs: [Wireshark-bugs] [Bug 7471] "Bad" UAT entry can't be edited/removed via the Wire

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 02 Jan 2013 22:07:23 +0000

changed bug 7471

What Removed Added
CC   [email protected]

Comment # 1 on bug 7471 from 
(In reply to comment #0)
> Obviously this is a pathological
> case. Are other types of UAT field validations handled in a similar manner
> (i.e., don't load the entry if the validation fails) ?

Yes.  If any field fails validation, the UAT entry is removed when the UAT is
loaded.  For a "protocol" field, the protocol must exist.

> If so, I could imagine there's other situations wherein a UAT entry becomes invalid after it's created and thus needs to be edited/removed.

The protocol field is validated within the UAT at the time the entry is created
in the GUI.  If "external forces" cause the field to be invalid, the entry is
removed, with no ability to edit it.

> Does Wireshark need to be able to handle this type of situation ?

I think the dissectors rely on the UAT entry data always being valid, so I
don't see any other choice but to throw invalid ones out when the UAT is
loaded.

You are receiving this mail because:
  • You are watching all bug changes.