mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
d3ace9b7ac
Zeek function types are serialized as a broker::vector, but the unserialization logic for Zeek set/table types that use a function for as an index incorrectly identified it as a composite-index, which also use broker::vector, rather than a singleton-index, and makes such unserialization fail. A general example where this failure can happen in practice is when trying to unserialize a connection record for which there's a Conn::RemovalHook, since that's a set[function], and a specific case of that is use of the Intel Framework in a Zeek cluster. |
||
|---|---|---|
| .. | ||
| store | ||
| connect-on-retry.zeek | ||
| disconnect.zeek | ||
| error.zeek | ||
| opaque.zeek | ||
| remote_event.zeek | ||
| remote_event_any.zeek | ||
| remote_event_auto.zeek | ||
| remote_event_index_types.zeek | ||
| remote_event_ssl_auth.zeek | ||
| remote_event_vector_any.zeek | ||
| remote_id.zeek | ||
| remote_log.zeek | ||
| remote_log_batch.zeek | ||
| remote_log_late_join.zeek | ||
| remote_log_types.zeek | ||
| ssl-mismatch.zeek | ||
| ssl_auth_failure.zeek | ||
| unpeer.zeek | ||