Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D1A639FB410; Tue, 26 Sep 2006 12:52:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 95562-09; Tue, 26 Sep 2006 12:52:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B81F09FB25B; Tue, 26 Sep 2006 12:52:49 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k8QFqdZp026304; Tue, 26 Sep 2006 11:52:39 -0400 (EDT) To: "Jeanna Geier" cc: "Jeff Frost" , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: pg_hba.conf: 'trust' vs. 'md5' Issues In-reply-to: <00cf01c6e180$6e21a500$6700a8c0@geier> References: <006201c6e171$bee28c70$6700a8c0@geier> <00cf01c6e180$6e21a500$6700a8c0@geier> Comments: In-reply-to "Jeanna Geier" message dated "Tue, 26 Sep 2006 10:28:33 -0500" Date: Tue, 26 Sep 2006 11:52:39 -0400 Message-ID: <26303.1159285959@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.097 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/298 X-Sequence-Number: 23212 "Jeanna Geier" writes: > [ hostssl works with 'trust' but not 'md5' ] > It's only when I change the connection method to 'md5' that I'm running into > problems -- then I cannot connect from pgadmin or the command line. I experimented with this using CVS HEAD, and found that SSL+md5 works fine as long as I enter the correct password ... but if I give a wrong password I get $ psql -h localhost regression Password: psql: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "tgl", database "regression", SSL off $ which is at best pretty misleading :-(. I think libpq is probably mishandling the "bad password" error and concluding that it should fall back to a non-SSL connection, which the server then rejects. Will look into it. As for Jeanna's problem, I don't see any password prompt at all in her example. I've forgotten the details, but wasn't there a password prompting problem with 8.0.x on Windows? regards, tom lane