Re: DETAIL for wrong scram password

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Jacob Champion <pchampion(at)vmware(dot)com>
Cc: "jeff(dot)janes(at)gmail(dot)com" <jeff(dot)janes(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DETAIL for wrong scram password
Date: 2021-03-25 07:41:16
Message-ID: YFw+nI6rtEuo9VPv@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 02, 2021 at 05:48:05PM +0000, Jacob Champion wrote:
> What would you think about adding the additional detail right after
> verify_client_proof() fails? I.e.

Agreed. Having that once all the code paths have been taken and the
client proof has been verified looks more solid. On top of what's
proposed, would it make sense to have a second logdetail for the case
of a mock authentication? We don't log that yet, so I guess that it
could be useful for audit purposes?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2021-03-25 07:51:21 Re: Minimal logical decoding on standbys
Previous Message Kyotaro Horiguchi 2021-03-25 07:37:10 Re: wal stats questions