I think there's a mixture of both "Heuristic Protocols" and "Heuristic dissectors" and I'm not sure how clean the list would look if you merged the two into a single list (this just being anecdotal evidence browsing the lists in both tabs).
The original motivation for this patch came from bugs 11152, 11335 and 11336 where it was only the heuristic dissector that was desired to be turned off ("identifier-based" desired to remain on). There are also protocols that have multiple heuristic dissectors (based on the protocol the dissector is supposed to run on top of), so I'm not sure if its as simple as "disabling protocol altogether" vs "disabling (all?) dissector heuristics of a protocol".
-----Original Message-----
From: Guy Harris <guy@xxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Sent: Sun, Jul 5, 2015 11:32 pm
Subject: Re: [Wireshark-dev] Enabling/disabling ANY heuristic dissector
On Jul 5, 2015, at 8:14 PM, Hadriel Kaplan <hadrielk@xxxxxxxxx> wrote:
>
BTW, in case someone’s curious, attached is a screenshot of the dialog window
tab Michael’s change adds.
>
> <Screen Shot 2015-07-05 at 8.52.05
PM.png>
"Heuristic Protocol" or "Heuristic Dissector"?
Should we have a
single table, listing protocols, with up to two checkboxes, one for the
"identifier-based" dissector (if any; leave the checkbox out if none) and one
for the heuristic dissector (if any; leave the checkbox out if none)?
Or, if
there's never a case where you'd want to disable the "identifier-based"
dissector but not the heuristic dissector, a checkbox to completely disable the
dissector ("identifier-based" and heuristic) and, if there's a heuristic
dissector, a checkbox to disable only
it?
___________________________________________________________________________
Sent
via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:
https://www.wireshark.org/lists/wireshark-dev
Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
