ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 7471] New: "Bad" UAT entry can't be removed via the Wiresh

Date: Thu, 12 Jul 2012 17:02:54 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7471

           Summary: "Bad" UAT entry can't be removed via the Wireshark GUI
                    ??
           Product: Wireshark
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: wmeier@xxxxxxxxxxx


Build Information:
SVN
--
It appears that a UAT entry with an error (at least for DLT_USER) can't be
removed via the UAT GUI.

Example:

1. Create a User DLT UAT entry specifying a protocol "xxx" (a plugin).
   Exit Wireshark.

2. Remove the "xxx" plugin.

3. Restart Wireshark;

   There will be a pop-up about a DLT load error: "can't find protocol".

4. So: go to DLT_USER pref to remove the table entry.

   Surprise: there's no entry (because there was an error loading it ?).

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) ?

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.

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

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.