Wireshark Lua initialization searches all directories recursively in its search path for *.lua files. If your client puts his network drive in this search path, then it seems logical that Wireshark *should* look there. Perhaps there should be a preference option to disable this (to prevent unintentional loading of Lua files).
For more on the Wireshark Lua search path: http://ask.wireshark.org/questions/8328/order-of-entries-in-dissector-tables-at-startup-and-lua/8387 -Tony On Wed, Apr 18, 2012 at 11:24 AM, Anders Broman <[email protected]>wrote: > Hi, > I recently had to troubleshoot a colleges Wireshark problem(Windows). He > got unexpected dissection of a USER_DLT even though it was defined to a > specific protocol it got dissected as a different one > Not present in Wireshark. Looking in enabled protocols this protocol was > present there as well. After much scratching of heads we disabled LUA and > the problem disappeared. > Further analysis revealed that he had a network drive H: mounted for his > Unix account and there in .wireshark a .lua file lurked. > Should Wireshark realy pick up files from there? > > Regards > Anders > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected]?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
