Re: [PATCH] Accept IP addresses in server certificate SANs
Jacob Champion <pchampion@vmware.com>
From: Jacob Champion <pchampion@vmware.com>
To: "horikyota.ntt@gmail.com" <horikyota.ntt@gmail.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2022-01-04T22:58:14Z
Lists: pgsql-hackers
Attachments
- since-v1.diff.txt (text/plain)
- v2-0001-Move-inet_net_pton-to-src-port.patch (text/x-patch) patch v2-0001
- v2-0002-libpq-allow-IP-address-SANs-in-server-certs.patch (text/x-patch) patch v2-0002
On Thu, 2021-12-16 at 18:44 +0000, Jacob Champion wrote: > It sounds like both you and Andrew might be comfortable with that same > behavior? I think it looks like a sane solution, so I'll implement that > and we can see what it looks like. (My work on this will be paused over > the end-of-year holidays.) v2 implements the discussed CN/SAN fallback behavior and should fix the build on Windows. Still TODO is the internal pg_inet_pton() refactoring that you asked for; I'm still deciding how best to approach it. Changes only in since-v1.diff.txt. Thanks, --Jacob
Commits
-
libpq: Allow IP address SANs in server certificates
- c1932e542863 15.0 landed
-
Add SSL tests for IP addresses in certificates
- af9e18049550 15.0 landed
-
Make JSON path numeric literals more correct
- e26114c817b6 15.0 cited