Re: Connection string

From: "Harpreet Dhaliwal" <harpreet(dot)dhaliwal01(at)gmail(dot)com>
To: "Michael Fuhr" <mike(at)fuhr(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Connection string
Date: 2006-08-13 23:27:40
Message-ID: d86a77ef0608131627y54e8b1ache12177668cfcc619@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yeah. I just realized when I could not start pgadminIII in the DB server
computer.
Added that line for localhost too :)

Yeah, i need stronger authentication for my application.
Thanks for the valuable advice.

Thanks again

~Harpreet.

On 8/13/06, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
>
> On Sun, Aug 13, 2006 at 07:07:11PM -0400, Harpreet Dhaliwal wrote:
> > Problem was with pg_hba.conf file
> >
> > ECPGdebug(1, stderr); showed that in pg_hba.conf there was setting for
> > localhost only and not for other ip addresses.
> >
> > I had to change the configuration for IPV4 local connections
> >
> > It should have been something like
> >
> > host all all 192.168.0.0/24 trust
> > instead of
> > host all all 127.0.0.1/32 trust (which is meant for localhost
> > only)
> >
> > I think i got it...right?
>
> You might want to add 192.168.0.0/24 on another line rather than
> replacing 127.0.0.1. And allowing "trust" connections is bad
> security practice because anybody on one of the allowed IP addresses
> could connect as any user without being challenged for a password.
> Consider using a stronger authentication method and modifying the
> client code accordingly.
>
> http://www.postgresql.org/docs/8.1/interactive/auth-methods.html
>
> --
> Michael Fuhr
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Broersma Jr 2006-08-13 23:36:02 Re: Connection string
Previous Message Michael Fuhr 2006-08-13 23:18:46 Re: Connection string