| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Serverside SNI support in libpq |
| Date: | 2025-02-19 23:12:50 |
| Message-ID: | F4222274-15C0-40E4-84FB-8FC1355BB8B2@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Attached is a rebase which fixes a few smaller things (and a pgperltidy run);
and adds a paragraph to the docs about how HBA clientname settings can't be
made per certificate set in an SNI config. As discussed with Jacob offlist,
there might be a case for supporting that but it will be a niche usecase within
a niche feature, so rather than complicating the code for something which might
never be used, it's likely better to document it and await feedback.
Are there any blockers for getting this in?
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Serverside-SNI-support-for-libpq.patch | application/octet-stream | 45.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-02-19 23:19:10 | Re: dblink: Add SCRAM pass-through authentication |
| Previous Message | Thomas Munro | 2025-02-19 23:12:21 | Re: BitmapHeapScan streaming read user and prelim refactoring |