Christian Kreibich 421639e7a7 Explicitly don't support sets with multiple index types in input/config frameworks ... 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.		2021-01-11 13:35:46 -08:00
..
files	Support for log filter policy hooks	2020-09-30 12:32:45 -07:00
frameworks	Explicitly don't support sets with multiple index types in input/config frameworks	2021-01-11 13:35:46 -08:00
misc	Tweak find-filtered-trace to not flag traces if they have non-TCP	2020-09-25 11:29:44 +00:00
packet-protocols	Remove default_analyzer for Ethernet packet analzyer	2020-11-09 19:54:45 -07:00
protocols	TLS 1.3 changes: Address review feedback	2020-12-18 10:51:36 +00:00
utils	Reverts the regex change in dead3226a5.	2020-11-18 15:35:17 -07:00
init-bare.zeek	Move UnknownProtocol options to init-bare.zeek	2020-11-11 12:58:38 -08:00
init-default.zeek	Add backtrace() and print_backtrace()	2020-07-03 14:09:31 -07:00
init-frameworks-and-bifs.zeek	GH-1122: Allow initializing globals with calls to subdir BIFs	2020-08-27 12:20:37 -07:00