From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Jacob Champion <jchampion(at)timescale(dot)com>, Shaun Thomas <shaun(dot)thomas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Logging of matching pg_hba.conf entry during auth skips trust auth, potential security issue |
Date: | 2023-08-21 13:27:51 |
Message-ID: | CA+TgmoYQ8_5vqEe0O4JkSx2H50sCrKZJxr7EG3JEzDJHezA8fA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Aug 20, 2023 at 7:58 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Attached is a v3 to do these two things, with adjustments for two SSL
> tests. Any objections about it?
+ * No authentication identity was set; this happens e.g. when the
+ * trust method is in use. For audit purposes, log a breadcrumb to
+ * explain where in the HBA this happened.
Proposed rewrite: "Normally, if log_connections is set, the call to
set_authn_id will log the connection. However, if that function is
never called, perhaps because the trust method is in use, then we
handle the logging here instead."
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-08-21 13:32:27 | Re: BUG #18059: Unexpected error 25001 in stored procedure |
Previous Message | Ashutosh Bapat | 2023-08-21 13:06:04 | Re: persist logical slots to disk during shutdown checkpoint |