Re: Serverside SNI support in libpq
Jacob Champion <jacob.champion@enterprisedb.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Michael Paquier <michael@paquier.xyz>,
Pgsql Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-02-24T21:51:02Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
ssl: Serverside SNI support for libpq
- 4f433025f666 19 (unreleased) landed
-
ssl: Add tests for client CA
- 25e568ba7ce7 19 (unreleased) landed
Attachments
- tests.diff.txt (text/plain)
On Wed, Feb 19, 2025 at 3:13 PM Daniel Gustafsson <daniel@yesql.se> wrote: > Are there any blockers for getting this in? > + SSL_context = ssl_init_context(isServerStart, host); I'm still not quite following the rationale behind the SSL_context assignment. To maybe illustrate, attached are some tests that I expected to pass, but don't. After adding an additional host and reloading the config, the behavior of the original fallback host seems to change. Am I misunderstanding the designed fallback behavior, have I misdesigned my test, or is this a bug? Thanks, --Jacob