From: Tom Lane <tgl@sss.pgh.pa.us>
To: ytourki@ext.scaleway.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18095: Unintended non-SSL connection attempt by psql cli
 command after a failed password authentication
In-reply-to: <18095-1efc746f742f766c@postgresql.org>
References: <18095-1efc746f742f766c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 07 Sep 2023 16:44:13 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1722733.1694107053.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 07 Sep 2023 13:17:33 -0400
Message-ID: <1722734.1694107053@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1722734.1694107053%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> When connecting to a PostgreSQL server (version 14) configured to only
> accept SSL connections, if a user provides an incorrect password, the ps=
ql
> client (version 14) returns two error messages in succession. The first
> message correctly indicates a password authentication failure, but the
> second suggests an unexpected non-SSL connection attempt.

This is libpq's (not psql's) default behavior.  If you don't like it,
you need to set the sslmode parameter in the connection string to prevent
non-SSL connection attempts.  See

https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-SSLMODE-S=
TATEMENTS

			regards, tom lane