Ethereal-dev: Re: [Ethereal-dev] (re)dissecting another dissector's field

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Thomas Anders <thomas.anders@xxxxxxxxxxxxx>
Date: Sun, 30 May 2004 23:21:00 +0200
Guy Harris wrote:

Have "dissect_kerberos_main()" take an argument that supplies callback
routines for the Kerberos dissector to use on those specific subfields?


But how does the Kerberos dissector know what "those specific subfields"
are? It may be one of several candidates. Should it try the callback on
each?


That doesn't solve the arbitrary problem of alllowing arbitrary
dissector X to supply its own dissectors for arbitrary fields generated
by arbitrary dissector Y, but I don't know whether there's a clean
solution to that general problem.


If dissector X knows the "name" of this field, shouldn't it have the
possibility to retrieve the relevant details (tree/item/hf) and
overwrite the existing dissection? Technically possible?


+Thomas

--
Thomas Anders <thomas.anders@xxxxxxxxxxxxx>