Re: SSL SNI

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Cc: Jacob Champion <pchampion(at)vmware(dot)com>
Subject: Re: SSL SNI
Date: 2021-03-18 11:27:02
Message-ID: 4eaa2b56-c3d0-67b6-4716-010d001c7601@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 25.02.21 19:36, Jacob Champion wrote:
> On Thu, 2021-02-25 at 17:00 +0100, Peter Eisentraut wrote:
>> Just as additional data points, it has come to my attention that both
>> the Go driver ("lib/pq") and the JDBC environment already send SNI
>> automatically. (In the case of JDBC this is done by the Java system
>> libraries, not the JDBC driver implementation.)
>
> For the Go case it's only for sslmode=verify-full, and only because the
> Go standard library implementation does it for you automatically if you
> request the builtin server hostname validation. (I checked both lib/pq
> and its de facto replacement, jackc/pgx.) So it may not be something
> that was done on purpose by the driver implementation.

Here is a new patch with an option to turn it off, and some
documentation added.

Attachment Content-Type Size
v3-0001-libpq-Set-Server-Name-Indication-SNI-for-SSL-conn.patch text/plain 7.4 KB

In response to

  • Re: SSL SNI at 2021-02-25 18:36:22 from Jacob Champion

Responses

  • Re: SSL SNI at 2021-04-07 13:32:55 from Peter Eisentraut

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthieu Garrigues 2021-03-18 11:28:02 Re: [HACKERS] PATCH: Batch/pipelining support for libpq
Previous Message Amit Kapila 2021-03-18 11:11:41 Re: Parallel INSERT (INTO ... SELECT ...)