Re: MD5 password issue - Mailing list pgsql-general

From Tom Lane
Subject Re: MD5 password issue
Date
Msg-id 8332.1232041193@sss.pgh.pa.us
Whole thread Raw
In response to MD5 password issue  (Andreas Wenk <a.wenk@netzmeister-st-pauli.de>)
Responses Re: MD5 password issue  (Andreas Wenk <a.wenk@netzmeister-st-pauli.de>)
List pgsql-general
Andreas Wenk <a.wenk@netzmeister-st-pauli.de> writes:
> In pg_hba.conf we have:

> # TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD

> # "local" is for Unix domain socket connections only
> local   all         all                               ident sameuser

> # IPv4 local connections:
> host    all         all         127.0.0.1/32          md5
> host    all         all         192.168.97.0/24       md5

> Now the question: why is the user pgadmin able to connect to the database using pgAdmin
> III from 192.168.97.30? That sould not be possible ... or am I wrong?

Why shouldn't it be possible?  You've specifically allowed connections
from that IP range.

(If you're wondering why he didn't have to type his password,
it's likely because pgAdmin is getting it out of ~/.pgpass or
some private settings file.)

            regards, tom lane

pgsql-general by date:

Previous
From: Sam Mason
Date:
Subject: Re: Why would I want to use connection pooling middleware?
Next
From: Kirk Strauser
Date:
Subject: Re: Why would I want to use connection pooling middleware?