mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
Merge remote-tracking branch 'origin/topic/awelzel/3424-http-upgrade-websocket-v1'
* origin/topic/awelzel/3424-http-upgrade-websocket-v1: websocket: Handle breaking from WebSocket::configure_analyzer() websocket: Address review feedback for BinPac code fuzzers: Add WebSocket fuzzer websocket: Fix crash for fragmented messages websocket: Verify Sec-WebSocket-Key/Accept headers and review feedback btest/websocket: Test for coalesced reply-ping HTTP/CONNECT: Also weird on extra data in reply HTTP/Upgrade: Weird when more data is available ContentLine: Add GetDeliverStreamRemainingLength() accessor HTTP: Drain event queue after instantiating upgrade analyzer btest/http: Explain switching-protocols test change as comment WebSocket: Introduce new analyzer and log HTTP: Add mechanism to instantiate Upgrade analyzer
This commit is contained in:
commit
822ca99e80
86 changed files with 1896 additions and 25 deletions
16
NEWS
16
NEWS
|
@ -101,6 +101,22 @@ New Functionality
|
|||
Given this is the first iteration of this feature, feedback around usability and
|
||||
use-cases that aren't covered are more than welcome.
|
||||
|
||||
- A WebSocket analyzer has been added together with a new ``websocket.log``.
|
||||
|
||||
The WebSocket analyzer is instantiated when a WebSocket handshake over HTTP is
|
||||
recognized. By default, the payload of WebSocket messages is fed into Zeek's dynamic
|
||||
protocol detection framework, possibly discovering and analyzing tunneled protocols.
|
||||
|
||||
The format of the log and the event semantics should be considered preliminary until
|
||||
the arrival of the next long-term-stable release (7.0).
|
||||
|
||||
To disable the analyzer in case of fatal errors or unexpected resource usage,
|
||||
use the ``Analyzer::disabled_analyzers`` pattern:
|
||||
|
||||
redef Analyzer::disabled_analyzers += {
|
||||
Analyzer::ANALYZER_WEBSOCKET,
|
||||
};
|
||||
|
||||
- The SMTP analyzer was extended to recognize and properly handle the BDAT command
|
||||
from RFC 3030. This improves visibility into the SMTP protocol when mail agents
|
||||
and servers support and use this extension.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue