From: | Jacob Champion <pchampion(at)vmware(dot)com> |
---|---|
To: | "peter(dot)eisentraut(at)enterprisedb(dot)com" <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Log details for client certificate failures |
Date: | 2022-05-12 22:36:01 |
Message-ID: | 9b8338210b865d79239ec35ca523792ce331c0a3.camel@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2022-05-05 at 15:12 +0000, Jacob Champion wrote:
> On Wed, 2022-05-04 at 15:53 +0200, Peter Eisentraut wrote:
> > In terms of aligning what is printed, I meant that pg_stat_ssl uses the
> > issuer plus serial number to identify the certificate unambiguously.
>
> Oh, that's a great idea. I'll do that too.
v2 limits the maximum subject length and adds the serial number to the
logs.
Thanks!
--Jacob
Attachment | Content-Type | Size |
---|---|---|
since-v1.diff.txt | text/plain | 12.8 KB |
v2-0001-Log-details-for-client-certificate-failures.patch | text/x-patch | 13.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-05-12 23:42:07 | Re: Comments on Custom RMGRs |
Previous Message | Simon Riggs | 2022-05-12 21:26:51 | Re: Comments on Custom RMGRs |