mirror of
https://github.com/zeek/zeek.git
synced 2025-10-04 07:38:19 +00:00
f6615753f1
The previous fix also made it clear that the ssl_history field may grow unbounded via the ssl_alert event. Prevent by capping using a configurable limit (default 100) and raise a weird once reached.
12 lines
650 B
Text
12 lines
650 B
Text
# Test max history length functionality
|
|
|
|
# @TEST-EXEC: zeek -r $TRACES/tls/tls-conn-with-extensions.trace
|
|
# @TEST-EXEC: zeek-cut uid ssl_history < ssl.log > ssl-max-history-length-default.log
|
|
# @TEST-EXEC: btest-diff ssl-max-history-length-default.log
|
|
# @TEST-EXEC: ! test -f weird.log
|
|
#
|
|
# @TEST-EXEC: zeek -r $TRACES/tls/tls-conn-with-extensions.trace SSL::max_ssl_history_length=3
|
|
# @TEST-EXEC: zeek-cut uid ssl_history < ssl.log > ssl-max-history-length-3.log
|
|
# @TEST-EXEC: zeek-cut uid name < weird.log > weird-max-history-length-3.log
|
|
# @TEST-EXEC: btest-diff ssl-max-history-length-3.log
|
|
# @TEST-EXEC: btest-diff weird-max-history-length-3.log
|