Re: [PATCH] Log details for client certificate failures
От | Peter Eisentraut |
---|---|
Тема | Re: [PATCH] Log details for client certificate failures |
Дата | |
Msg-id | 61aa4b6c-9de2-d61b-821a-a34ab1e515e2@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Log details for client certificate failures (Jacob Champion <jchampion@timescale.com>) |
Ответы |
Re: [PATCH] Log details for client certificate failures
|
Список | pgsql-hackers |
On 05.07.22 18:34, Jacob Champion wrote: > On Fri, Jul 1, 2022 at 1:51 PM Jacob Champion <jchampion@timescale.com> wrote: >> Sorry for the misunderstanding! v3 adds the Issuer to the logs as well. > > Resending v3; I messed up the certificate diff with my gitconfig. This patch looks pretty good to me. Some minor details: I looked into how you decode the serial number. I have found some code elsewhere that passed the result of X509_get_serialNumber() directly to ASN1_INTEGER_set(). But I guess a serial number of maximum length 20 octets wouldn't fit into a 32-bit long. (There is ASN1_INTEGER_set_int64(), but that requires OpenSSL 1.1.0.) Does that match your understanding? For the detail string, I think we could do something like: DETAIL: Failed certificate data (unverified): subject '%s', serial number %s, issuer '%s'
В списке pgsql-hackers по дате отправления: