mirror of
https://github.com/zeek/zeek.git
synced 2025-10-03 23:28:20 +00:00
a7343ee019
With the recent packet manager work, it broke to register a protocol
analyzer for a specific port from inside a plugin's initialization code.
That's because that registration now depends on the packet manager being
set up, which isn't case at that time a plugin's `InitPostInit()` runs.
This fix contains two parts:
- Initialize the packet manager before the analyzer manager, so that
the latter's `InitPostScript()` can rely on the former being
ready.
- Change the analyzer manager to (only) record port registrations
happening before it's fully initialized. Its `InitPostScript()`
then performs the actual registrations, knowing it can use the
packet manager now.
This comes with a `cmake/` to add a missing include directory.
|
||
|---|---|---|
| .. | ||
| binpac-flowbuffer-frame-length-plugin | ||
| file-plugin | ||
| func-hook-plugin | ||
| hooks-plugin | ||
| logging-hooks-plugin | ||
| packet-protocol-plugin | ||
| pktdumper-plugin | ||
| pktsrc-plugin | ||
| plugin-load-dependency | ||
| plugin-nopatchversion-plugin | ||
| plugin-withpatchversion-plugin | ||
| protocol-plugin | ||
| reader-plugin | ||
| reporter-hook-plugin | ||
| writer-plugin | ||
| bifs-and-scripts-install.sh | ||
| bifs-and-scripts.sh | ||
| binpac-flowbuffer-frame-length.zeek | ||
| file.zeek | ||
| func-hook.zeek | ||
| hooks.zeek | ||
| init-plugin.zeek | ||
| logging-hooks.zeek | ||
| packet-protocol.zeek | ||
| pktdumper.zeek | ||
| pktsrc.zeek | ||
| plugin-load-dependency.zeek | ||
| plugin-nopatchversion.zeek | ||
| plugin-withpatchversion.zeek | ||
| protocol.zeek | ||
| reader.zeek | ||
| reporter-hook.zeek | ||
| writer.zeek | ||