I know the question of how to remove unneeded
dissectors arises from time to time. However I am not
under the illusion that it will be faster. What I does
concern me however is that with recent problems found
in string handling, I am wondering if it makes sense
to remove unused dissectors for the sheer purpose of
removing the exposure they present. Having tried this
without a lot of success, I have found that the
interdependencies are very difficult to map out.
Currently I have tethereal deployed on multiple
sniffers with read filters to try to limit the scope
of capture/exposure.
So what I want to know is if anyone has any
ideas/plans on how a document could be put together
listing some kind of dependency tree. So that you
could remove those items that you do not depend on,
without some random assert going off.
Thanks in advance for any ideas.
=====
Jaime Fournier
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
