pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeanna Geier <jgeier@apt-cafm.com>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: pg_hba.conf: 'trust' vs. 'md5' Issues
Date: Tue, 26 Sep 2006 11:52:39 -0400
Message-ID: <26303.1159285959@sss.pgh.pa.us> (raw)
In-Reply-To: <00cf01c6e180$6e21a500$6700a8c0@geier>
References: <006201c6e171$bee28c70$6700a8c0@geier>
	<Pine.LNX.4.64.0609260755100.32444@discord.home.frostconsultingllc.com>
	<Pine.LNX.4.64.0609260804180.32444@discord.home.frostconsultingllc.com>
	<00cf01c6e180$6e21a500$6700a8c0@geier>

"Jeanna Geier" <jgeier@apt-cafm.com> 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



view thread (21+ messages)  latest in thread

Message-ID: <26303.1159285959@sss.pgh.pa.us>
Permalink:  ../26303.1159285959@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26303.1159285959@sss.pgh.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jgeier@apt-cafm.com, jeff@frostconsultingllc.com, pgsql-hackers@postgresql.org
  Subject: Re: pg_hba.conf: 'trust' vs. 'md5' Issues
  In-Reply-To: <26303.1159285959@sss.pgh.pa.us>
  References: <006201c6e171$bee28c70$6700a8c0@geier> <Pine.LNX.4.64.0609260755100.32444@discord.home.frostconsultingllc.com> <Pine.LNX.4.64.0609260804180.32444@discord.home.frostconsultingllc.com> <00cf01c6e180$6e21a500$6700a8c0@geier> <26303.1159285959@sss.pgh.pa.us>

* 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