zeek/testing/btest/Traces/ftp
Arne Welzel 3f5cb75a2a ftp: Introduce FTP::max_command_length
oss-fuzz produced FTP traffic with a ~550KB long FTP command. Cap FTP command
length at 100 bytes, log a weird if a command is larger than that and move
on to the next. Likely it's not actual FTP traffic, but raising an
analyzer violation would allow clients an easy way to disable the analyzer
by sending an overly long command.

The added test PCAP was generated using a fake Python socket server/client.
2022-11-21 09:36:29 +01:00
..
bigtransfer.pcap Fix reassembly of data w/ sizes beyond 32-bit capacities (BIT-348). 2014-04-09 13:03:24 -05:00
bruteforce.pcap Add unit tests for new Bro Manual docs. 2014-01-21 16:01:55 -06:00
cwd-navigation.pcap Fixing FTP cwd getting overlue long. 2016-05-29 08:52:47 -07:00
fake-long-commands.pcap ftp: Introduce FTP::max_command_length 2022-11-21 09:36:29 +01:00
fake-server-delays-all.pcap ftp: Limit pending commands to FTP::max_pending_commands (default 20) 2022-11-08 16:44:17 -07:00
ftp-with-numbers-in-filename.pcap Files transferred over FTP were showing incorrect sizes. 2016-03-11 12:56:28 -05:00
ipv4.trace FileAnalysis: add unit tests covering current protocol integration. 2013-03-19 15:50:05 -05:00
ipv6-violation.trace Introduce generic analyzer_confirmation_info and analyzer_violation_info 2022-09-27 17:49:51 +02:00
ipv6.trace FileAnalysis: add unit tests covering current protocol integration. 2013-03-19 15:50:05 -05:00
retr.trace FileAnalysis: add unit tests covering current protocol integration. 2013-03-19 15:50:05 -05:00