Re: [PATCH] Log details for client certificate failures
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Jacob Champion <jchampion@timescale.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2022-07-15T16:34:17Z
Lists: pgsql-hackers
On 14.07.22 23:09, Jacob Champion wrote: > On Thu, Jul 14, 2022 at 1:12 PM Peter Eisentraut > <peter.eisentraut@enterprisedb.com> wrote: >> Concretely, I was thinking like the attached top-up patch. >> >> The other way can surely be made to work somehow, but this seems much >> simpler and with fewer questions about the details. > > Ah, seeing it side-by-side helps. That's much easier, I agree. Committed like that.
Commits
-
Fix tiny memory leaks
- a9d58bfe8a3a 16.0 landed
-
Don't reflect unescaped cert data to the logs
- 257eb57b50f7 16.0 landed
-
pg_clean_ascii(): escape bytes rather than lose them
- 45b1a67a0fcb 16.0 landed
-
Log details for client certificate failures
- 3a0e385048ad 16.0 landed