NEWS: Update news for tunnel depth changes

This commit is contained in:
Arne Welzel 2024-01-10 15:36:12 +01:00
parent 7325bc945f
commit 040068f390

8
NEWS
View file

@ -153,6 +153,10 @@ New Functionality
Note that generally you should prefer record extension in conditionally loaded Note that generally you should prefer record extension in conditionally loaded
scripts rather than using conditional directives in the original record definition. scripts rather than using conditional directives in the original record definition.
- The 'X' code can now appear in a connection's history. It is meant to indicate
situations where Zeek stopped analyzing traffic due to exceeding certain limits or
when encountering unknown/unsupported protocols. Its first use is to indicate
``Tunnel::max_depth`` being exceeded.
Changed Functionality Changed Functionality
--------------------- ---------------------
@ -172,6 +176,10 @@ Changed Functionality
detail API from ``digest.h`` to compute hashes likely need to accommodate for detail API from ``digest.h`` to compute hashes likely need to accommodate for
this change. this change.
- The ``Tunnel::max_depth`` default was changed from 2 to 4 allowing for more than
two encapsulation layers. Two layers are already easily reached in AWS GLB
environments.
Removed Functionality Removed Functionality
--------------------- ---------------------