From: Markus KARG <markus@headcrashing.eu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
Date: Wed, 25 Dec 2024 18:45:06 +0100
Message-ID: <036d3915-e6ef-420b-ba2b-5cd7e94e0a66@headcrashing.eu> (raw)
In-Reply-To: <1794654.1735148362@sss.pgh.pa.us>
References: <68ff85d7-9b41-40ec-bddf-0ca74fe09875@headcrashing.eu>
<1794654.1735148362@sss.pgh.pa.us>
> Markus KARG<markus@headcrashing.eu> writes:
>> Summary: The TLS behavior of psql changed between 16.3 and 16.4 as shown
>> below.
> Have you tried the current release (16.6)?
>
> regards, tom lane
Yes, but psql 16.6 fails in the same way:
root@hetzner-2:~# docker run -it postgres:16.6 psql
"host=headcrashing.eu port=5432 dbname=postgres user=postgres
password=HeadcrashingPostgres2022 sslmode=require"
psql: error: connection to server at "headcrashing.eu" (49.13.53.107),
port 5432 failed: SSL error: tlsv1 alert no application protocol
-Markus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: markus@headcrashing.eu, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
In-Reply-To: <036d3915-e6ef-420b-ba2b-5cd7e94e0a66@headcrashing.eu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox