BUG #17919: "client hello" message / SNI / Openshift Routes

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: ronald(dot)van(dot)de(dot)kuil(at)nl(dot)ibm(dot)com
Subject: BUG #17919: "client hello" message / SNI / Openshift Routes
Date: 2023-05-03 13:16:47
Message-ID: 17919-6149a80f52802c2f@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17919
Logged by: Ronald van de Kuil
Email address: ronald(dot)van(dot)de(dot)kuil(at)nl(dot)ibm(dot)com
PostgreSQL version: 15.2
Operating system: windows server 2019
Description:

I have deployed postgresql in Openshift with a certificate that matches its
openshift route name.

Then it should be possible to connect to the database instance via targeting
the route in psql. The way that works, is that the openshift router looks at
the SNI, and then it will be able to route it into the Pod that has the
certificate with the same CN or SAN.

I have wiresharked the connection, and noticed that psql does not send a
client hello message.

I would make a guess that this is related to the version of libpq, based on
something which has been seen before on another project that is using
postgresql in combination with terraform, see:
https://github.com/cyrilgdn/terraform-provider-postgresql/pull/295

When I take a look at the latest source code then I believe that provision
have been made for setting up SNI connections:

https://github.com/postgres/postgres/blob/master/doc/src/sgml/libpq.sgml#L1946

Is this a bug?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stan S 2023-05-03 13:38:43 Re: BUG #17914: walsenders taking up all memory
Previous Message Devrim Gündüz 2023-05-03 12:56:20 Re: BUG #17918: Checksum failed while sync repos for a package