From: | AJ ONeal <coolaj86(at)proton(dot)me> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Feature Request: Add "pg" as TLS-ALPN |
Date: | 2024-05-11 15:34:02 |
Message-ID: | y3hCpl3ALJQPlIn8aKG19aiYbNM_HbchVTOqlwm2Y9OE-sWmtre-Cljlt9Jd_yYsv5S3mDNG-T5OXXfU8GgDrdu2MjTBEcWl23_NUesj8i8=@proton.me |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In the same place that SNI is being passed to openssl during the client-initiated TLS, could we get ALPN set to "pg" by default (and perhaps an --alpn <proto|empty-string> and/or --no-alpn) to assist in protocol routing / virtual hosting?
P.S. I'm willing to personally fund the development of these two features I've requested. It would come out of my own pocket (no investors or enterprise behind me) - but I do a variety of development for a variety of clients and I believe that these changes will indirectly end up putting enough money back in my own pocket to make it worth it over the years. I could contract a member of the core team or, if we got to a sure-fire "will accept given these conditions", I could find someone in my friend or work group to commission to make the changes.
AJ ONeal
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-05-11 15:59:04 | Re: Feature Request: Option for TLS no SSLRequest with psql |
Previous Message | AJ ONeal | 2024-05-11 15:19:50 | Feature Request: Option for TLS no SSLRequest with psql |