Horton
Menu

Re: Experiments with Postgres and SSL

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: Heikki Linnakangas <hlinnaka@iki.fi>, Matthias van de Meent <boekewurm+postgres@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>, Greg Stark <stark@mit.edu>, Andrey Borodin <amborodin86@gmail.com>, Vladimir Sitnikov <sitnikov.vladimir@gmail.com>, Michael Paquier <michael@paquier.xyz>
Date: 2024-04-24T20:51:29Z
Lists: pgsql-hackers 
On 08.04.24 10:38, Heikki Linnakangas wrote:
> On 08/04/2024 04:25, Heikki Linnakangas wrote:
>> One important open item now is that we need to register a proper ALPN
>> protocol ID with IANA.
> 
> I sent a request for that: 
> https://mailarchive.ietf.org/arch/msg/tls-reg-review/9LWPzQfOpbc8dTT7vc9ahNeNaiw/

Why did you ask for "pgsql"?  The IANA protocol name for port 5432 is 
"postgres".  This seems confusing.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Enhance libpq encryption negotiation tests with new GUC

  2. With gssencmode='require', check credential cache before connecting

  3. Add tests for libpq gssencmode and sslmode options

  4. Move Kerberos module

  5. Give nicer error message when connecting to a v10 server requiring SCRAM.