From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Provide more detail in postmaster log for password authenticatio |
Date: | 2016-01-07 16:19:39 |
Message-ID: | E1aHDHn-0006Kl-F1@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Provide more detail in postmaster log for password authentication failures.
We tell people to examine the postmaster log if they're unsure why they are
getting auth failures, but actually only a few relatively-uncommon failure
cases were given their own log detail messages in commit 64e43c59b817a78d.
Expand on that so that every failure case detected within md5_crypt_verify
gets a specific log detail message. This should cover pretty much every
ordinary password auth failure cause.
So far I've not noticed user demand for a similar level of auth detail
for the other auth methods, but sooner or later somebody might want to
work on them. This is not that patch, though.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/5e0b5dcab685fe2a342385450a29a825cf40cddf
Modified Files
--------------
src/backend/libpq/crypt.c | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-01-07 16:27:00 | pgsql: Remove vestigial CHECK_FOR_INTERRUPTS call. |
Previous Message | Alvaro Herrera | 2016-01-07 15:01:40 | pgsql: Windows: Make pg_ctl reliably detect service status |