| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | rray(at)tcmail(dot)mstc(dot)state(dot)ms(dot)us |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Login with blank password |
| Date: | 2004-12-11 16:32:41 |
| Message-ID: | 16621.1102782761@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
rray(at)tcmail(dot)mstc(dot)state(dot)ms(dot)us writes:
> Is there a setting in postgresql.conf that will log the password that's used to login with?
No (deliberately so).
> If I add "host all user 172.17.32.0 255.255.255.0 password"
> to pg_hba.conf the user can login with a blank password.
> If I add "host all user 172.17.32.1 255.255.255.255 password"
> to pg_hba.conf the user must enter a correct password.
This sounds to me like you are failing to consider the effects of the
order of entries in pg_hba.conf --- ie, in the first case the connection
is being caught by a TRUST-mode entry (or at least, not a password-based
one ... could be IDENT as well). Don't forget to SIGHUP the postmaster
after editing pg_hba.conf, too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-11 16:37:50 | Re: Backup is too slow |
| Previous Message | Devrim GUNDUZ | 2004-12-11 13:03:45 | Re: postgresql 7.4.1 SRPM |