| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Wenk <a(dot)wenk(at)netzmeister-st-pauli(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: MD5 password issue |
| Date: | 2009-01-15 17:39:53 |
| Message-ID: | 8332.1232041193@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andreas Wenk <a(dot)wenk(at)netzmeister-st-pauli(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirk Strauser | 2009-01-15 17:41:51 | Re: Why would I want to use connection pooling middleware? |
| Previous Message | Sam Mason | 2009-01-15 17:25:28 | Re: Why would I want to use connection pooling middleware? |