mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
130c89a0a7
To address review feedback in GH-4362: rename analyzer-failed-log.zeek to loggig.zeek, analyzer-debug-log.zeek to debug-logging.zeek and dpd-log.zeek to deprecated-dpd-log.zeek. Includes respective test, NEWS, etc updates.
34 lines
1.1 KiB
Text
34 lines
1.1 KiB
Text
@deprecated("Please switch to frameworks/analyzer/packet-segment-logging, which logs to analyzer.log. Remove in 8.1")
|
|
|
|
##! This script enables logging of packet segment data when a protocol
|
|
##! parsing violation is encountered. The amount of data from the
|
|
##! packet logged is set by the :zeek:see:`DPD::packet_segment_size` variable.
|
|
##! A caveat to logging packet data is that in some cases, the packet may
|
|
##! not be the packet that actually caused the protocol violation.
|
|
|
|
@load frameworks/analyzer/deprecated-dpd-log
|
|
|
|
module DPD;
|
|
|
|
export {
|
|
redef record Info += {
|
|
## A chunk of the payload that most likely resulted in the
|
|
## analyzer violation.
|
|
packet_segment: string &optional &log;
|
|
};
|
|
|
|
## Size of the packet segment to display in the DPD log.
|
|
option packet_segment_size: int = 255;
|
|
}
|
|
|
|
|
|
event analyzer_violation_info(atype: AllAnalyzers::Tag, info: AnalyzerViolationInfo) &priority=4
|
|
{
|
|
if ( ! is_protocol_analyzer(atype) && ! is_packet_analyzer(atype) )
|
|
return;
|
|
|
|
if ( ! info?$c || ! info$c?$dpd )
|
|
return;
|
|
|
|
info$c$dpd$packet_segment = fmt("%s", sub_bytes(get_current_packet()$data, 0, packet_segment_size));
|
|
}
|