Re: connecting to a remote pq always require a password

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: connecting to a remote pq always require a password
Date: 2009-06-20 03:56:03
Message-ID: h1hmkj$8i7$1@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2009-06-18, David Shen <davidshen84(at)googlemail(dot)com> wrote:
> Hi,
>
> I am trying to use the libpq to connect to my postgresql 8.3 server.
> If I use "dbname = mydb", the connection made successfully because I
> am using a socket connection. But if I use "host = 127.0.0.1 dbname =
> mydb", the error message is "no password supplied".
>
> In the pg_hba.conf file, I even change the host access control to this:
> host all all 127.0.0.1/32 trust
>
> but it still does not work. What I missed?

postgres doesn't know who you are! specify a user in the connection
string.

you can use "ident sameuser" over TCP connections but it is no more
secure than the originating host. (it works via RFC1413)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2009-06-20 04:03:07 Re: postgresql-8.3.7 unexpected connection closures
Previous Message Scott Marlowe 2009-06-20 03:29:51 Re: Disaster recovery (server died)