mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
242db4981d
Skimming through the RFC, the previous approach of having containers for most fields seems unfounded for normal protocol operation. The new weirds could just as well be considered protocol violations. Outside of duplicated or missed data they just shouldn't happen for well-behaved client/server behavior. Additionally, with non-conformant traffic it would be trivial to cause unbounded state growth and immense log record sizes. Unfortunately, things have become a bit clunky now. Closes #3504 |
||
|---|---|---|
| .. | ||
| __load__.zeek | ||
| consts.zeek | ||
| dpd.sig | ||
| main.zeek | ||
| spicy-events.zeek | ||