Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: hostnossl in pg_hba.conf demands a password
From: John Scalia <jayknowsunix@gmail.com>
In-Reply-To: <13378.1479160375@sss.pgh.pa.us>
Date: Mon, 14 Nov 2016 17:37:07 -0500
Cc: Venkata B Nagothi <nag1010@gmail.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FADA7A56-4601-4513-8321-551A148EA717@gmail.com>
References: <BE1F46E9-B06A-4FE4-A2BF-D470E2488CEA@gmail.com>
 <CAEyp7J_Y5sG0MSUyPCFPencprUAVeHEbfH=sv6vpwxtzgkEumQ@mail.gmail.com>
 <5878107F-B5AB-4AEB-8B52-987AF3DB1739@gmail.com>
 <13378.1479160375@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Thanks, Tom,

I'll check to see if it's trying an SSL comnection, but being that I logged=
 into this server, and I know that I don't have an .ssh subdirectory in my =
home dir, I didn't think an SSL connection would be tried. We'll see.

Thanks again,
Jay


Sent from my iPad

> On Nov 14, 2016, at 4:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> John Scalia <jayknowsunix@gmail.com> writes:
>> The only entries are a local connection line with md5 authentication spe=
cified and a line for local replication with a trust authentication. Both o=
f these entries do seem to be working properly.
>=20
> So the client is trying an SSL connection first (which would be the
> default behavior for libpq at least), and that falls through the
> hostnossl line and is captured by the md5 line.  Hence you get a
> password prompt.  The client has no way to know that a non-SSL
> connection would have gotten a different response.
>=20
> You could change the md5 line to hostssl, perhaps.  Or configure
> the client to try non-SSL first (see sslprefer).
>=20
>            regards, tom lane


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin