Fupeng Zhao e4e56789db Report PostgreSQL login success only after ReadyForQuery ... Previously, Zeek treated the receipt of `AuthenticationOk` as a successful login. However, according to the PostgreSQL Frontend/Backend Protocol, the startup phase is not complete until the server sends `ReadyForQuery`. It is still possible for the server to emit an `ErrorResponse` (e.g. ERRCODE_INVALID_AUTHORIZATION_SPECIFICATION) after `AuthenticationOk` but before `ReadyForQuery`. This change updates the PostgreSQL analyzer to defer reporting login success until `ReadyForQuery` is observed. This prevents false positives in cases where authentication succeeds but session startup fails.		2025-08-18 10:59:44 +08:00
..
files	Expand the size of the log-size filters for x509	2025-08-12 17:31:28 -07:00
frameworks	Add options to filter at the stream level as well as globally	2025-08-12 17:31:28 -07:00
misc	Fix errors from rst linting on the generated docs	2025-01-24 11:41:36 -07:00
packet-protocols	Add analyzer registration from VLAN to VNTAG	2025-03-18 11:51:27 -07:00
protocols	Report PostgreSQL login success only after ReadyForQuery	2025-08-18 10:59:44 +08:00
utils	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00
init-bare.zeek	Revert "Move BinPAC, bifcl, af_packet, and gen_zam submodules into main zeek repo"	2025-08-15 15:11:22 -07:00
init-default.zeek	spciy-redis: Bring Redis analyzer into Zeek proper	2025-05-27 09:28:12 -04:00
init-frameworks-and-bifs.zeek	Minor comment tweaks for init-frameworks-and-bifs.zeek	2024-10-18 09:56:29 -07:00
init-supervisor.zeek	Establish a separate init script when using the supervisor	2021-07-08 13:12:53 -07:00