public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: AJ ONeal <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Feature Request: Option for TLS no SSLRequest with psql
Date: Sat, 11 May 2024 11:59:04 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <ECNyobMWPeoCd4yj_5J0RsDL1yKC9MbbBwOGCYHgcts7v0BW_-znGIoxcvfzUsf3yKvUB6Lef22OBMZnJyZ-0T2U1qaVflQqEGO0RFHp1PE=@proton.me>
References: <ECNyobMWPeoCd4yj_5J0RsDL1yKC9MbbBwOGCYHgcts7v0BW_-znGIoxcvfzUsf3yKvUB6Lef22OBMZnJyZ-0T2U1qaVflQqEGO0RFHp1PE=@proton.me>

AJ ONeal <[email protected]> writes:
> Could we get a `postgrestls://` or `sslmode=tls` or --tls option that instructs psql​ to sends straight TLS, skipping the 0000000804d2162f / 0000000804d21630 + N / Y / S handshake?

You're too late:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d39a49c1e4

(and likewise too late about ALPN).

You might however care to weigh in on the ongoing argument about what
the libpq connection options controlling this should do (but not on
this list):

https://www.postgresql.org/message-id/flat/ad45965c-8b95-4bde-bf05-509ab6fccf96%40iki.fi

			regards, tom lane

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Feature Request: Option for TLS no SSLRequest with psql
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox