mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
![]() 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. |
||
---|---|---|
.. | ||
availability.zeek | ||
bad-backend-message.zeek | ||
bad-startup-message.zeek | ||
dump-events.zeek | ||
http-on-port-5432.zeek | ||
mysql-on-port-5432.zeek | ||
parameter-status.zeek | ||
psql-auth.zeek | ||
psql-aws-ssl-disable-15432.zeek | ||
psql-aws-ssl-disable.zeek | ||
psql-aws-ssl-require-15432.zeek | ||
psql-aws-ssl-require.zeek | ||
psql-create-insert-select.zeek | ||
psql-insert-fail-drop-fail.zeek | ||
psql-login-fail.zeek | ||
psql-login-no-role.zeek | ||
psql-login-no-sslrequest.zeek | ||
psql-select-now.zeek | ||
startup-parameter.zeek |