Btests: don't use -C in Zeek invocations that don't actually need it

This commit is contained in:
Christian Kreibich 2025-06-06 13:39:31 -07:00
parent e3cecdf04d
commit 8b39e59572
91 changed files with 96 additions and 96 deletions

View file

@ -1,4 +1,4 @@
# @TEST-EXEC: zeek -C -b -r $TRACES/erspan.trace %INPUT
# @TEST-EXEC: zeek -b -r $TRACES/erspan.trace %INPUT
# @TEST-EXEC: btest-diff tunnel.log
@load base/frameworks/tunnels

View file

@ -1,4 +1,4 @@
# @TEST-EXEC: zeek -C -b -r $TRACES/erspanI.pcap %INPUT
# @TEST-EXEC: zeek -b -r $TRACES/erspanI.pcap %INPUT
# @TEST-EXEC: btest-diff tunnel.log
# @TEST-EXEC: btest-diff conn.log

View file

@ -1,4 +1,4 @@
# @TEST-EXEC: zeek -C -b -r $TRACES/erspanII.pcap %INPUT
# @TEST-EXEC: zeek -b -r $TRACES/erspanII.pcap %INPUT
# @TEST-EXEC: btest-diff tunnel.log
# @TEST-EXEC: btest-diff conn.log

View file

@ -1,4 +1,4 @@
# @TEST-EXEC: zeek -C -b -r $TRACES/erspanIII.pcap %INPUT
# @TEST-EXEC: zeek -b -r $TRACES/erspanIII.pcap %INPUT
# @TEST-EXEC: btest-diff tunnel.log
# @TEST-EXEC: btest-diff conn.log

View file

@ -1,5 +1,5 @@
# @TEST-EXEC: zeek -C -b -r $TRACES/wikipedia.trace %INPUT >>output
# @TEST-EXEC: zeek -C -b -r $TRACES/radiotap.pcap %INPUT >>output
# @TEST-EXEC: zeek -b -r $TRACES/wikipedia.trace %INPUT >>output
# @TEST-EXEC: zeek -b -r $TRACES/radiotap.pcap %INPUT >>output
# @TEST-EXEC: btest-diff output
event new_connection(c: connection)

View file

@ -1,3 +1,3 @@
# @TEST-EXEC: zeek -C -r $TRACES/wikipedia.trace -f "port 50000"
# @TEST-EXEC: zeek -r $TRACES/wikipedia.trace -f "port 50000"
# @TEST-EXEC: btest-diff conn.log
# @TEST-EXEC: btest-diff packet_filter.log

View file

@ -1,5 +1,5 @@
# Disable test temporarily - see GH-4547
# @TEST-REQUIRES: ! have-spicy-ssl
# @TEST-EXEC: zeek -C -r $TRACES/pppoe-over-qinq.pcap
# @TEST-EXEC: zeek -r $TRACES/pppoe-over-qinq.pcap
# @TEST-EXEC: btest-diff conn.log

View file

@ -1,4 +1,4 @@
# @TEST-EXEC: zeek -C -b -r $TRACES/wlanmon.pcap %INPUT | sort | uniq -c | awk '{print $1, $2, $3}' >output
# @TEST-EXEC: zeek -b -r $TRACES/wlanmon.pcap %INPUT | sort | uniq -c | awk '{print $1, $2, $3}' >output
# @TEST-EXEC: btest-diff output
# The sampling functionality itself is already tested through other tests.

View file

@ -1,5 +1,5 @@
# @TEST-DOC: Tests a GRE ARUBA trace that contains IEEE 802.11 QoS A-MSDU headers. This is testing that the tunnel is detected and that the conn byte size contains both A-MSDU subframe packets.
# @TEST-EXEC: zeek -C -b -r $TRACES/tunnels/gre-aruba-amsdu.pcap %INPUT
# @TEST-EXEC: zeek -b -r $TRACES/tunnels/gre-aruba-amsdu.pcap %INPUT
# @TEST-EXEC: btest-diff tunnel.log
# @TEST-EXEC: btest-diff conn.log

View file

@ -1,4 +1,4 @@
# @TEST-DOC: Tests a GRE ARUBA trace that contains IEEE 802.11 CCMP headers. This should report a weird about encrypted data.
# @TEST-EXEC: zeek -C -b -r $TRACES/tunnels/gre-aruba-ccmp.pcap %INPUT
# @TEST-EXEC: zeek -b -r $TRACES/tunnels/gre-aruba-ccmp.pcap %INPUT
@load base/frameworks/notice/weird

View file

@ -1,4 +1,4 @@
# @TEST-EXEC: zeek -C -b -r $TRACES/tunnels/gre-aruba.pcap %INPUT
# @TEST-EXEC: zeek -b -r $TRACES/tunnels/gre-aruba.pcap %INPUT
# @TEST-EXEC: btest-diff tunnel.log
@load base/frameworks/tunnels

View file

@ -1,3 +1,3 @@
# @TEST-DOC: Tests that an IP-in-IP tunnel with max-depth set to 1 doesn't crash
# @TEST-EXEC: zeek -C -r $TRACES/tunnels/gre-within-gre.pcap Tunnel::max_depth=1
# @TEST-EXEC: zeek -r $TRACES/tunnels/gre-within-gre.pcap Tunnel::max_depth=1
# @TEST-EXEC: btest-diff weird.log

View file

@ -1,4 +1,4 @@
# @TEST-EXEC: zeek -C -r $TRACES/tunnels/gtp/gtp9_unknown_or_too_short_payload.pcap %INPUT
# @TEST-EXEC: zeek -r $TRACES/tunnels/gtp/gtp9_unknown_or_too_short_payload.pcap %INPUT
# @TEST-EXEC: btest-diff analyzer.log
# @TEST-EXEC: btest-diff tunnel.log