mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
421639e7a7
The input framework's Manager::IsCompatibleType() already rejected sets with multiple index types that aren't all the same (i.e. that are not pure). Pure ones (e.g. "set[addr,addr]") slipped through and could cause Zeek to segfault elsewhere in the config framework due to type comparison subtleties. Note that the ASCII reader can't read such sets anyway, so this method now rejects sets with any kind of index-type tuple. In the config framework, the script-level change handler has a risky conversion from any to set[bool], which can trigger segfaults when the underlying set's index is a type tuple. We now prevent this code path by ensuring it only applies to sets with a single index type. |
||
|---|---|---|
| .. | ||
| __load__.zeek | ||
| input.zeek | ||
| main.zeek | ||
| README | ||
| weird.zeek | ||
The configuration framework provides a way to change the Zeek configuration in "option" values at run-time.