Skip site navigation (1) Skip section navigation (2)

Re: pg_hba.conf

From: mike g <mike(at)thegodshalls(dot)com>
To: LSanchez(at)ameritrade(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_hba.conf
Date: 2004-05-27 03:16:15
Message-ID: 1085627775.4674.8.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-admin
Hello,

I finally got it to work and as some have mentioned it was not the
encryption level.

I had setup my pg_hba.conf originally like this:

host   all     all     10.15.0.0       255.255.255.0   trust


I was under the impression that the .0 was supposed to be equivalent to
a wildcard entry so that any connection from 10.15 would be able to
connect.  This was not so.  By changing my pg_hba.conf to this:

host   all     all    10.15.13.0      255.255.255.0    trust

I was able to connect successfully.  The .0 works as a wildcard entry
for the last part but not the one prior.  


Hope that helps you.

Mike


On Wed, 2004-05-26 at 10:25, LSanchez(at)ameritrade(dot)com wrote:
> Thanks so much! :)
> 
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us] 
> Sent: Wednesday, May 26, 2004 10:56 AM
> To: LSanchez(at)ameritrade(dot)com
> Cc: mike(at)thegodshalls(dot)com; xzilla(at)users(dot)sourceforge(dot)net;
> pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] pg_hba.conf
> 
> LSanchez(at)ameritrade(dot)com wrote:
> > Thanks Mike!
> > 
> > Do you know if pgSQL will be supporting higher level of encryption in
> > the near future? Most of us here at Ameritrade work from home via VPN.
> 
> 
> We support SSL so you don't need VPN encryption.  However, we should
> work with whatever VPN encryption you are already using too.

In response to

Responses

pgsql-admin by date

Next:From: C. BensendDate: 2004-05-27 03:35:47
Subject: Re: pg_hba.conf
Previous:From: Chris BrowneDate: 2004-05-26 19:02:52
Subject: Re: pg_hba.conf

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group