mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
af77a7a83b
The main part of this commit are changes in tests. A lot of the tests that previously relied on analyzer.log or dpd.log now use the new analyzer-failed.log. I verified all the changes and, as far as I can tell, everything behaves as it should. This includes the external test baselines. This change also enables logging of file and packet analyzer to analyzer_failed.log and fixes some small behavior issues. The analyzer_failed event is no longer raised when the removal of an analyzer is vetoed. If an analyzer is no longer active when an analyzer violation is raised, currently the analyzer_failed event is raised. This can, e.g., happen when an analyzer error happens at the very end of the connection. This makes the behavior more similar to what happened in the past, and also intuitively seems to make sense. A bug introduced in the failed service logging was fixed.
16 lines
537 B
Text
16 lines
537 B
Text
# @TEST-DOC: Tests handling of PDUs containing error ioctls with byte lengths of zero
|
|
# @TEST-EXEC: zeek -b -r $TRACES/smb/smb2-zero-byte-error-ioctl.pcap %INPUT 2>&1 >out
|
|
# @TEST-EXEC: ! test -f analyzer_failed.log
|
|
# @TEST-EXEC: btest-diff out
|
|
|
|
@load base/protocols/smb
|
|
|
|
event smb2_close_request(c: connection, hdr: SMB2::Header, file_id: SMB2::GUID)
|
|
{
|
|
print "smb2_close_request", hdr;
|
|
}
|
|
|
|
event smb2_close_response(c: connection, hdr: SMB2::Header, response: SMB2::CloseResponse)
|
|
{
|
|
print "smb2_close_response", hdr, response;
|
|
}
|