pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_hba.conf
53+ messages / 25 participants
[nested] [flat]
* pg_hba.conf
@ 2000-11-01 11:51 Eduardo Kotujansky <eduardo@complex.com.br>
0 siblings, 1 reply; 53+ messages in thread
From: Eduardo Kotujansky @ 2000-11-01 11:51 UTC (permalink / raw)
To: pgsql-admin
I have a machine with Linux/PostgreSQL in my local network with ip
192.168.1.10
I tryed to conect from another machine (192.168.1.3) with pgaccess
I got a message error: no entry for 192.168.1.3 db x user y..etc...in
pg_hba.conf
I tryed to put a line in pg_hba.conf to allow this, and did not work, so I
removed that line.
After that I can not even conect from the back-end machine (192.168.1.10)
the message is that: "missing or erroneous pg_hba.conf file"
Any direction please ?
Eduardo K
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2000-11-01 13:43 Giovanni Serrato Castillo <gserrato@sager.telecom-co.net>
parent: Eduardo Kotujansky <eduardo@complex.com.br>
0 siblings, 0 replies; 53+ messages in thread
From: Giovanni Serrato Castillo @ 2000-11-01 13:43 UTC (permalink / raw)
To: Eduardo Kotujansky <eduardo@complex.com.br>; pgsql-admin
Modifica los permisos de lectura del archivo pg_hba.conf.
----- Original Message -----
From: "Eduardo Kotujansky" <eduardo@complex.com.br>
To: <pgsql-admin@postgresql.org>
Sent: Wednesday, November 01, 2000 6:51 AM
Subject: [ADMIN] pg_hba.conf
> I have a machine with Linux/PostgreSQL in my local network with ip
> 192.168.1.10
> I tryed to conect from another machine (192.168.1.3) with pgaccess
> I got a message error: no entry for 192.168.1.3 db x user y..etc...in
> pg_hba.conf
>
> I tryed to put a line in pg_hba.conf to allow this, and did not work, so I
> removed that line.
> After that I can not even conect from the back-end machine (192.168.1.10)
> the message is that: "missing or erroneous pg_hba.conf file"
>
> Any direction please ?
>
> Eduardo K
>
>
^ permalink raw reply [nested|flat] 53+ messages in thread
* pg_hba.conf
@ 2003-02-27 19:59 Sidar Lopez Cruz <sidarlopez@hotmail.com>
0 siblings, 1 reply; 53+ messages in thread
From: Sidar Lopez Cruz @ 2003-02-27 19:59 UTC (permalink / raw)
To: pgsql-admin
how can i config this file to connect from any ip on my lan
:-) Sidar Lopez Cruz
- Cero Riesgo, S.A.
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2003-02-27 22:50 Robert Treat <xzilla@users.sourceforge.net>
parent: Sidar Lopez Cruz <sidarlopez@hotmail.com>
0 siblings, 1 reply; 53+ messages in thread
From: Robert Treat @ 2003-02-27 22:50 UTC (permalink / raw)
To: Sidar Lopez Cruz <sidarlopez@hotmail.com>; +Cc: pgsql-admin
host all 192.168.0.0 255.255.0.0 trust
that should work, though it's pretty insecure. note you might need to
address your lan ip address if it's not 192.168.*.*
Robert Treat
On Thu, 2003-02-27 at 14:59, Sidar Lopez Cruz wrote:
> how can i config this file to connect from any ip on my lan
>
> :-) Sidar Lopez Cruz
> - Cero Riesgo, S.A.
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2003-02-28 20:16 Ed L. <pgsql@bluepolka.net>
parent: Robert Treat <xzilla@users.sourceforge.net>
0 siblings, 0 replies; 53+ messages in thread
From: Ed L. @ 2003-02-28 20:16 UTC (permalink / raw)
To: Robert Treat <xzilla@users.sourceforge.net>; Sidar Lopez Cruz <sidarlopez@hotmail.com>; +Cc: pgsql-admin
On Thursday February 27 2003 3:50, Robert Treat wrote:
> On Thu, 2003-02-27 at 14:59, Sidar Lopez Cruz wrote:
> > how can i config this file to connect from any ip on my lan
> >
> host all 192.168.0.0 255.255.0.0 trust
>
> that should work, though it's pretty insecure. note you might need
> to address your lan ip address if it's not 192.168.*.*
That applies only for pre-7.3 releases, I believe. Pg 7.3.x
introduced new syntax for pg_hba.conf. You'll need an extra 'all'
after the 'all' above for 7.3.x.
Ed
^ permalink raw reply [nested|flat] 53+ messages in thread
* pg_hba.conf
@ 2003-10-16 04:40 Ganesan Kanavathy <ganesh@magnusquest.com>
0 siblings, 0 replies; 53+ messages in thread
From: Ganesan Kanavathy @ 2003-10-16 04:40 UTC (permalink / raw)
To: pgsql-admin
If I do any changes in pg_hba.conf file do I need restart pgsql.
The changes I made does not taking effect.
ganesh
^ permalink raw reply [nested|flat] 53+ messages in thread
* pg_hba.conf
@ 2003-10-16 06:44 Ashok Chauhan <ashok@kalculate.com>
0 siblings, 2 replies; 53+ messages in thread
From: Ashok Chauhan @ 2003-10-16 06:44 UTC (permalink / raw)
To: pgsql-admin
>>If I do any changes in pg_hba.conf file do I need restart pgsql.
>>The changes I made does not taking effect.
>>ganesh
Yes, you need to restart pgsql.
the changes you made it does not effect.
but also my suggestion is that to perform any changes in pg_hba.conf or
any pgsql configration file , please stop the postgresql and then make
changes and restart it again.
Ashok
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2003-10-16 06:50 Will LaShell <will@lashell.net>
parent: Ashok Chauhan <ashok@kalculate.com>
1 sibling, 0 replies; 53+ messages in thread
From: Will LaShell @ 2003-10-16 06:50 UTC (permalink / raw)
To: Ashok Chauhan <ashok@kalculate.com>; +Cc: pgsql-admin
Ashok Chauhan wrote:
>
>
>>>If I do any changes in pg_hba.conf file do I need restart pgsql.
>>>The changes I made does not taking effect.
>>>ganesh
>>>
>>>
>
>Yes, you need to restart pgsql.
>the changes you made it does not effect.
>
>but also my suggestion is that to perform any changes in pg_hba.conf or
>any pgsql configration file , please stop the postgresql and then make
>changes and restart it again.
>
>
>
This is uncessary for pg_hba.conf edits. Simply call pg_ctl reload to
reread the access list.
Will
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2003-10-16 14:43 Christopher Browne <cbbrowne@libertyrms.info>
parent: Ashok Chauhan <ashok@kalculate.com>
1 sibling, 0 replies; 53+ messages in thread
From: Christopher Browne @ 2003-10-16 14:43 UTC (permalink / raw)
To: pgsql-admin
ashok@kalculate.com (Ashok Chauhan) writes:
>>>If I do any changes in pg_hba.conf file do I need restart pgsql.
>>>The changes I made does not taking effect.
>>>ganesh
>
> Yes, you need to restart pgsql.
> the changes you made it does not effect.
No, you do NOT need to restart the postmaster; that is just one of a
number of methods of making these sorts of changes take effect.
Methods include:
1. Well, yes, restarting the postmaster.
2. The command "pg_ctl reload"
3. The command "kill -HUP [process ID of postmaster]"
2 and 3 do the same thing, despite appearing different...
--
let name="cbbrowne" and tld="libertyrms.info" in String.concat "@" [name;tld];;
<http://dev6.int.libertyrms.com/;
Christopher Browne
(416) 646 3304 x124 (land)
^ permalink raw reply [nested|flat] 53+ messages in thread
* pg_hba.conf
@ 2004-05-20 23:52 LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-20 23:52 UTC (permalink / raw)
To: pgsql-admin
I'm trying to access our test postgreSQL server via VPN and even though
I already setup the host for the vpn's ip address, I'm still getting an
error similar to "host for vpn address does not exist"
What am I doing incorrectly?
Thanks!
- Lily Anne
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-21 20:40 Robert Treat <xzilla@users.sourceforge.net>
parent: LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: Robert Treat @ 2004-05-21 20:40 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: pgsql-admin
On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> I'm trying to access our test postgreSQL server via VPN and even though
> I already setup the host for the vpn's ip address, I'm still getting an
> error similar to "host for vpn address does not exist"
>
> What am I doing incorrectly?
>
The error similar to that that I am thinking of would indicate that the
ip address of your client machine does not fall into the scheme laid out
in your pg_hba.conf. Most likely you need to add your home machines ip
into the pg_hba.conf (or open up one of the existing entries to include
the machine your connecting from)
HTH
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-21 21:01 LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-21 21:01 UTC (permalink / raw)
To: xzilla@users.sourceforge.net; +Cc: pgsql-admin
Thanks Robert!
I did that as well and still didn't work. Any other ideas?
-----Original Message-----
From: Robert Treat [mailto:xzilla@users.sourceforge.net]
Sent: Friday, May 21, 2004 4:41 PM
To: LSanchez@ameritrade.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> I'm trying to access our test postgreSQL server via VPN and even
though
> I already setup the host for the vpn's ip address, I'm still getting
an
> error similar to "host for vpn address does not exist"
>
> What am I doing incorrectly?
>
The error similar to that that I am thinking of would indicate that the
ip address of your client machine does not fall into the scheme laid out
in your pg_hba.conf. Most likely you need to add your home machines ip
into the pg_hba.conf (or open up one of the existing entries to include
the machine your connecting from)
HTH
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-22 00:04 Robert Treat <xzilla@users.sourceforge.net>
parent: LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: Robert Treat @ 2004-05-22 00:04 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: pgsql-admin
can you ping the server that postgresql is living on? or maybe your
misrepresenting the error message... what program are you using to try and
connect? can you verify that tcpip_sockets is turned on the server? also, if
it is a database problem there will be an exact error message being reported
in the logs of type FATAL, can you send us that?
Robert Treat
On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote:
> Thanks Robert!
>
> I did that as well and still didn't work. Any other ideas?
>
> -----Original Message-----
> From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> Sent: Friday, May 21, 2004 4:41 PM
> To: LSanchez@ameritrade.com
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> > I'm trying to access our test postgreSQL server via VPN and even
>
> though
>
> > I already setup the host for the vpn's ip address, I'm still getting
>
> an
>
> > error similar to "host for vpn address does not exist"
> >
> > What am I doing incorrectly?
>
> The error similar to that that I am thinking of would indicate that the
> ip address of your client machine does not fall into the scheme laid out
> in your pg_hba.conf. Most likely you need to add your home machines ip
> into the pg_hba.conf (or open up one of the existing entries to include
> the machine your connecting from)
>
> HTH
>
> Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-24 17:02 LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-24 17:02 UTC (permalink / raw)
To: xzilla@users.sourceforge.net; +Cc: pgsql-admin
Yes I can ping the server if not connected via VPN.
I'm using EMS PostgreSQL Manager, which works if not via VPN.
Yes, postgresql.conf's tcpip_socket = true.
The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113, user
postgres, database TEST.
Thanks for your help!
Regards,
- Lily Anne
-----Original Message-----
From: Robert Treat [mailto:xzilla@users.sourceforge.net]
Sent: Friday, May 21, 2004 8:04 PM
To: LSanchez@ameritrade.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
can you ping the server that postgresql is living on? or maybe your
misrepresenting the error message... what program are you using to try
and
connect? can you verify that tcpip_sockets is turned on the server?
also, if
it is a database problem there will be an exact error message being
reported
in the logs of type FATAL, can you send us that?
Robert Treat
On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote:
> Thanks Robert!
>
> I did that as well and still didn't work. Any other ideas?
>
> -----Original Message-----
> From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> Sent: Friday, May 21, 2004 4:41 PM
> To: LSanchez@ameritrade.com
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> > I'm trying to access our test postgreSQL server via VPN and even
>
> though
>
> > I already setup the host for the vpn's ip address, I'm still getting
>
> an
>
> > error similar to "host for vpn address does not exist"
> >
> > What am I doing incorrectly?
>
> The error similar to that that I am thinking of would indicate that
the
> ip address of your client machine does not fall into the scheme laid
out
> in your pg_hba.conf. Most likely you need to add your home machines ip
> into the pg_hba.conf (or open up one of the existing entries to
include
> the machine your connecting from)
>
> HTH
>
> Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 02:23 Mike G <mike@thegodshalls.com>
parent: LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: Mike G @ 2004-05-25 02:23 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: xzilla@users.sourceforge.net; pgsql-admin
Your ip address range is probably different when connecting via a VPN rather than in the office. By default postgres will not allow connections from other locations even if tcpip_socket is true without specifying an ip address range, database etc.
Checkout the docs. There is a section on pg_hba.conf.
Mike
On Mon, May 24, 2004 at 01:02:12PM -0400, LSanchez@ameritrade.com wrote:
> Yes I can ping the server if not connected via VPN.
>
> I'm using EMS PostgreSQL Manager, which works if not via VPN.
>
> Yes, postgresql.conf's tcpip_socket = true.
>
> The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113, user
> postgres, database TEST.
>
> Thanks for your help!
>
> Regards,
> - Lily Anne
>
>
> -----Original Message-----
> From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> Sent: Friday, May 21, 2004 8:04 PM
> To: LSanchez@ameritrade.com
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> can you ping the server that postgresql is living on? or maybe your
> misrepresenting the error message... what program are you using to try
> and
> connect? can you verify that tcpip_sockets is turned on the server?
> also, if
> it is a database problem there will be an exact error message being
> reported
> in the logs of type FATAL, can you send us that?
>
> Robert Treat
>
> On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote:
> > Thanks Robert!
> >
> > I did that as well and still didn't work. Any other ideas?
> >
> > -----Original Message-----
> > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > Sent: Friday, May 21, 2004 4:41 PM
> > To: LSanchez@ameritrade.com
> > Cc: pgsql-admin@postgresql.org
> > Subject: Re: [ADMIN] pg_hba.conf
> >
> > On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> > > I'm trying to access our test postgreSQL server via VPN and even
> >
> > though
> >
> > > I already setup the host for the vpn's ip address, I'm still getting
> >
> > an
> >
> > > error similar to "host for vpn address does not exist"
> > >
> > > What am I doing incorrectly?
> >
> > The error similar to that that I am thinking of would indicate that
> the
> > ip address of your client machine does not fall into the scheme laid
> out
> > in your pg_hba.conf. Most likely you need to add your home machines ip
> > into the pg_hba.conf (or open up one of the existing entries to
> include
> > the machine your connecting from)
> >
> > HTH
> >
> > Robert Treat
>
> --
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 13:42 LSanchez@ameritrade.com
0 siblings, 3 replies; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-25 13:42 UTC (permalink / raw)
To: mike@thegodshalls.com; +Cc: xzilla@users.sourceforge.net; pgsql-admin
Thanks Mike!
I already specified the IP address that was specified by my VPN
connection. I read through the docs and found nothing about anything
special with VPN connections.
Regards,
- Lily Anne
-----Original Message-----
From: Mike G [mailto:mike@thegodshalls.com]
Sent: Monday, May 24, 2004 10:23 PM
To: LSanchez@ameritrade.com
Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
Your ip address range is probably different when connecting via a VPN
rather than in the office. By default postgres will not allow
connections from other locations even if tcpip_socket is true without
specifying an ip address range, database etc.
Checkout the docs. There is a section on pg_hba.conf.
Mike
On Mon, May 24, 2004 at 01:02:12PM -0400, LSanchez@ameritrade.com wrote:
> Yes I can ping the server if not connected via VPN.
>
> I'm using EMS PostgreSQL Manager, which works if not via VPN.
>
> Yes, postgresql.conf's tcpip_socket = true.
>
> The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113, user
> postgres, database TEST.
>
> Thanks for your help!
>
> Regards,
> - Lily Anne
>
>
> -----Original Message-----
> From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> Sent: Friday, May 21, 2004 8:04 PM
> To: LSanchez@ameritrade.com
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> can you ping the server that postgresql is living on? or maybe your
> misrepresenting the error message... what program are you using to
try
> and
> connect? can you verify that tcpip_sockets is turned on the server?
> also, if
> it is a database problem there will be an exact error message being
> reported
> in the logs of type FATAL, can you send us that?
>
> Robert Treat
>
> On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote:
> > Thanks Robert!
> >
> > I did that as well and still didn't work. Any other ideas?
> >
> > -----Original Message-----
> > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > Sent: Friday, May 21, 2004 4:41 PM
> > To: LSanchez@ameritrade.com
> > Cc: pgsql-admin@postgresql.org
> > Subject: Re: [ADMIN] pg_hba.conf
> >
> > On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> > > I'm trying to access our test postgreSQL server via VPN and even
> >
> > though
> >
> > > I already setup the host for the vpn's ip address, I'm still
getting
> >
> > an
> >
> > > error similar to "host for vpn address does not exist"
> > >
> > > What am I doing incorrectly?
> >
> > The error similar to that that I am thinking of would indicate that
> the
> > ip address of your client machine does not fall into the scheme laid
> out
> > in your pg_hba.conf. Most likely you need to add your home machines
ip
> > into the pg_hba.conf (or open up one of the existing entries to
> include
> > the machine your connecting from)
> >
> > HTH
> >
> > Robert Treat
>
> --
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 14:50 Tom Lane <tgl@sss.pgh.pa.us>
parent: LSanchez@ameritrade.com
2 siblings, 0 replies; 53+ messages in thread
From: Tom Lane @ 2004-05-25 14:50 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net; pgsql-admin
<LSanchez@ameritrade.com> writes:
> I already specified the IP address that was specified by my VPN
> connection.
This is a long shot, but ... did you remember to SIGHUP the postmaster
after editing pg_hba.conf to allow that IP address?
regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 14:50 LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-25 14:50 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net; pgsql-admin
Yes sir, did that, too.
Thanks,
- Lily Anne
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, May 25, 2004 10:50 AM
To: LSanchez@ameritrade.com
Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
<LSanchez@ameritrade.com> writes:
> I already specified the IP address that was specified by my VPN
> connection.
This is a long shot, but ... did you remember to SIGHUP the postmaster
after editing pg_hba.conf to allow that IP address?
regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 17:02 Robert Treat <xzilla@users.sourceforge.net>
parent: LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: Robert Treat @ 2004-05-25 17:02 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: mike@thegodshalls.com; pgsql-admin
I am thinking that the entry for this ip has an issue with the username and/or
database specified in the line (or maybe conflicting entries?) Would you
mind posting your complete pg_hba.conf to the list?
Robert Treat
On Tuesday 25 May 2004 10:50, LSanchez@ameritrade.com wrote:
> Yes sir, did that, too.
>
> Thanks,
> - Lily Anne
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Tuesday, May 25, 2004 10:50 AM
> To: LSanchez@ameritrade.com
> Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
> pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> <LSanchez@ameritrade.com> writes:
> > I already specified the IP address that was specified by my VPN
> > connection.
>
> This is a long shot, but ... did you remember to SIGHUP the postmaster
> after editing pg_hba.conf to allow that IP address?
>
> regards, tom lane
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 17:13 LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-25 17:13 UTC (permalink / raw)
To: xzilla@users.sourceforge.net; +Cc: mike@thegodshalls.com; pgsql-admin
Here it is....
Thanks! :)
-----Original Message-----
From: Robert Treat [mailto:xzilla@users.sourceforge.net]
Sent: Tuesday, May 25, 2004 1:02 PM
To: LSanchez@ameritrade.com
Cc: mike@thegodshalls.com; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
I am thinking that the entry for this ip has an issue with the username
and/or
database specified in the line (or maybe conflicting entries?) Would
you
mind posting your complete pg_hba.conf to the list?
Robert Treat
On Tuesday 25 May 2004 10:50, LSanchez@ameritrade.com wrote:
> Yes sir, did that, too.
>
> Thanks,
> - Lily Anne
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Tuesday, May 25, 2004 10:50 AM
> To: LSanchez@ameritrade.com
> Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
> pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> <LSanchez@ameritrade.com> writes:
> > I already specified the IP address that was specified by my VPN
> > connection.
>
> This is a long shot, but ... did you remember to SIGHUP the postmaster
> after editing pg_hba.conf to allow that IP address?
>
> regards, tom lane
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Attachments:
pg_hba.conf (application/octet-stream, 2.6K) download
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 18:51 Tom Lane <tgl@sss.pgh.pa.us>
parent: LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: Tom Lane @ 2004-05-25 18:51 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: xzilla@users.sourceforge.net; mike@thegodshalls.com; pgsql-admin
<LSanchez@ameritrade.com> writes:
> Here it is....
> host all all 10.29.15.0 255.255.255.0 trust
That line certainly ought to match your connection. I think this has
got to be pilot error: either you didn't SIGHUP the postmaster or you
are editing the wrong copy of the file. (The right copy is
$PGDATA/pg_hba.conf.)
regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 18:54 LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-25 18:54 UTC (permalink / raw)
To: tgl@sss.pgh.pa.us; +Cc: xzilla@users.sourceforge.net; mike@thegodshalls.com; pgsql-admin
Um, I restarted postmaster so many times already after I made the entry
and this is the only pg_hba.conf file in our server (you're right,
$PGDATA/pg_hba.conf). It's a brand new server that had just been built.
Have you tried connecting to your pgSQL server via VPN?
Thanks!
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, May 25, 2004 2:51 PM
To: LSanchez@ameritrade.com
Cc: xzilla@users.sourceforge.net; mike@thegodshalls.com;
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
<LSanchez@ameritrade.com> writes:
> Here it is....
> host all all 10.29.15.0 255.255.255.0 trust
That line certainly ought to match your connection. I think this has
got to be pilot error: either you didn't SIGHUP the postmaster or you
are editing the wrong copy of the file. (The right copy is
$PGDATA/pg_hba.conf.)
regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 19:17 LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-25 19:17 UTC (permalink / raw)
To: tgl@sss.pgh.pa.us; +Cc: xzilla@users.sourceforge.net; mike@thegodshalls.com; pgsql-admin
Or it might be a security issue with how our VPN is setup. I'll talk to
our security folks and see what they will find.
Thanks!
-----Original Message-----
From: Sanchez, Lily
Sent: Tuesday, May 25, 2004 2:55 PM
To: 'Tom Lane'
Cc: xzilla@users.sourceforge.net; mike@thegodshalls.com;
pgsql-admin@postgresql.org
Subject: RE: [ADMIN] pg_hba.conf
Um, I restarted postmaster so many times already after I made the entry
and this is the only pg_hba.conf file in our server (you're right,
$PGDATA/pg_hba.conf). It's a brand new server that had just been built.
Have you tried connecting to your pgSQL server via VPN?
Thanks!
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, May 25, 2004 2:51 PM
To: LSanchez@ameritrade.com
Cc: xzilla@users.sourceforge.net; mike@thegodshalls.com;
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
<LSanchez@ameritrade.com> writes:
> Here it is....
> host all all 10.29.15.0 255.255.255.0 trust
That line certainly ought to match your connection. I think this has
got to be pilot error: either you didn't SIGHUP the postmaster or you
are editing the wrong copy of the file. (The right copy is
$PGDATA/pg_hba.conf.)
regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-25 20:33 Jim Seymour <jseymour@LinxNet.com>
parent: LSanchez@ameritrade.com
2 siblings, 0 replies; 53+ messages in thread
From: jseymour@LinxNet.com @ 2004-05-25 20:33 UTC (permalink / raw)
To: pgsql-admin
<LSanchez@ameritrade.com> wrote:
>
> Thanks Mike!
>
> I already specified the IP address that was specified by my VPN
> connection. I read through the docs and found nothing about anything
> special with VPN connections.
Which address? The address at your end of the connection may not be
the same as the address at the other end: The end trying to connect to
the pgsql server.
It appears from this
"The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113, ..."
the pgsql server sees (or saw) you coming from 10.29.15.113. So is
that address, or a superset of it, in pg_hba.conf? Has the server been
kicked in the pants to recognize the config change since it was added?
Jim
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 04:12 mike g <mike@thegodshalls.com>
parent: LSanchez@ameritrade.com
2 siblings, 1 reply; 53+ messages in thread
From: mike g @ 2004-05-26 04:12 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: xzilla@users.sourceforge.net; pgsql-admin
Hmm....
Looks like I am still in the same boat you are.
I still cannot log into my db over a VPN connection using pgadminIII.
Everytime I try and connect I get a "Server terminated connection
unexpectedly error".
I originally received the pg_hba.conf entry complaint as well but after
adding and restarting the system the above is all I get.
I tried specifying pgadmin to prefer SSL connection, and changed
pg_hba.conf entry to expect SSL from my VPN connection entry.
On Tue, 2004-05-25 at 08:42, LSanchez@ameritrade.com wrote:
> Thanks Mike!
>
> I already specified the IP address that was specified by my VPN
> connection. I read through the docs and found nothing about anything
> special with VPN connections.
>
> Regards,
> - Lily Anne
>
> -----Original Message-----
> From: Mike G [mailto:mike@thegodshalls.com]
> Sent: Monday, May 24, 2004 10:23 PM
> To: LSanchez@ameritrade.com
> Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> Your ip address range is probably different when connecting via a VPN
> rather than in the office. By default postgres will not allow
> connections from other locations even if tcpip_socket is true without
> specifying an ip address range, database etc.
>
> Checkout the docs. There is a section on pg_hba.conf.
>
> Mike
>
> On Mon, May 24, 2004 at 01:02:12PM -0400, LSanchez@ameritrade.com wrote:
> > Yes I can ping the server if not connected via VPN.
> >
> > I'm using EMS PostgreSQL Manager, which works if not via VPN.
> >
> > Yes, postgresql.conf's tcpip_socket = true.
> >
> > The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113, user
> > postgres, database TEST.
> >
> > Thanks for your help!
> >
> > Regards,
> > - Lily Anne
> >
> >
> > -----Original Message-----
> > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > Sent: Friday, May 21, 2004 8:04 PM
> > To: LSanchez@ameritrade.com
> > Cc: pgsql-admin@postgresql.org
> > Subject: Re: [ADMIN] pg_hba.conf
> >
> > can you ping the server that postgresql is living on? or maybe your
> > misrepresenting the error message... what program are you using to
> try
> > and
> > connect? can you verify that tcpip_sockets is turned on the server?
> > also, if
> > it is a database problem there will be an exact error message being
> > reported
> > in the logs of type FATAL, can you send us that?
> >
> > Robert Treat
> >
> > On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote:
> > > Thanks Robert!
> > >
> > > I did that as well and still didn't work. Any other ideas?
> > >
> > > -----Original Message-----
> > > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > > Sent: Friday, May 21, 2004 4:41 PM
> > > To: LSanchez@ameritrade.com
> > > Cc: pgsql-admin@postgresql.org
> > > Subject: Re: [ADMIN] pg_hba.conf
> > >
> > > On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> > > > I'm trying to access our test postgreSQL server via VPN and even
> > >
> > > though
> > >
> > > > I already setup the host for the vpn's ip address, I'm still
> getting
> > >
> > > an
> > >
> > > > error similar to "host for vpn address does not exist"
> > > >
> > > > What am I doing incorrectly?
> > >
> > > The error similar to that that I am thinking of would indicate that
> > the
> > > ip address of your client machine does not fall into the scheme laid
> > out
> > > in your pg_hba.conf. Most likely you need to add your home machines
> ip
> > > into the pg_hba.conf (or open up one of the existing entries to
> > include
> > > the machine your connecting from)
> > >
> > > HTH
> > >
> > > Robert Treat
> >
> > --
> > Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 4: Don't 'kill -9' the postmaster
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 04:51 mike g <mike@thegodshalls.com>
parent: mike g <mike@thegodshalls.com>
0 siblings, 1 reply; 53+ messages in thread
From: mike g @ 2004-05-26 04:51 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: xzilla@users.sourceforge.net; pgsql-admin
Hello,
I believe I found my problem. The Cisco VPN client I use encrypts data
at a 168 bit level. Postgres only supports up to 128 bit correct?
Mike
On Tue, 2004-05-25 at 23:12, mike g wrote:
> Hmm....
>
> Looks like I am still in the same boat you are.
>
> I still cannot log into my db over a VPN connection using pgadminIII.
>
> Everytime I try and connect I get a "Server terminated connection
> unexpectedly error".
>
> I originally received the pg_hba.conf entry complaint as well but after
> adding and restarting the system the above is all I get.
>
> I tried specifying pgadmin to prefer SSL connection, and changed
> pg_hba.conf entry to expect SSL from my VPN connection entry.
>
>
> On Tue, 2004-05-25 at 08:42, LSanchez@ameritrade.com wrote:
> > Thanks Mike!
> >
> > I already specified the IP address that was specified by my VPN
> > connection. I read through the docs and found nothing about anything
> > special with VPN connections.
> >
> > Regards,
> > - Lily Anne
> >
> > -----Original Message-----
> > From: Mike G [mailto:mike@thegodshalls.com]
> > Sent: Monday, May 24, 2004 10:23 PM
> > To: LSanchez@ameritrade.com
> > Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org
> > Subject: Re: [ADMIN] pg_hba.conf
> >
> > Your ip address range is probably different when connecting via a VPN
> > rather than in the office. By default postgres will not allow
> > connections from other locations even if tcpip_socket is true without
> > specifying an ip address range, database etc.
> >
> > Checkout the docs. There is a section on pg_hba.conf.
> >
> > Mike
> >
> > On Mon, May 24, 2004 at 01:02:12PM -0400, LSanchez@ameritrade.com wrote:
> > > Yes I can ping the server if not connected via VPN.
> > >
> > > I'm using EMS PostgreSQL Manager, which works if not via VPN.
> > >
> > > Yes, postgresql.conf's tcpip_socket = true.
> > >
> > > The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113, user
> > > postgres, database TEST.
> > >
> > > Thanks for your help!
> > >
> > > Regards,
> > > - Lily Anne
> > >
> > >
> > > -----Original Message-----
> > > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > > Sent: Friday, May 21, 2004 8:04 PM
> > > To: LSanchez@ameritrade.com
> > > Cc: pgsql-admin@postgresql.org
> > > Subject: Re: [ADMIN] pg_hba.conf
> > >
> > > can you ping the server that postgresql is living on? or maybe your
> > > misrepresenting the error message... what program are you using to
> > try
> > > and
> > > connect? can you verify that tcpip_sockets is turned on the server?
> > > also, if
> > > it is a database problem there will be an exact error message being
> > > reported
> > > in the logs of type FATAL, can you send us that?
> > >
> > > Robert Treat
> > >
> > > On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote:
> > > > Thanks Robert!
> > > >
> > > > I did that as well and still didn't work. Any other ideas?
> > > >
> > > > -----Original Message-----
> > > > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > > > Sent: Friday, May 21, 2004 4:41 PM
> > > > To: LSanchez@ameritrade.com
> > > > Cc: pgsql-admin@postgresql.org
> > > > Subject: Re: [ADMIN] pg_hba.conf
> > > >
> > > > On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> > > > > I'm trying to access our test postgreSQL server via VPN and even
> > > >
> > > > though
> > > >
> > > > > I already setup the host for the vpn's ip address, I'm still
> > getting
> > > >
> > > > an
> > > >
> > > > > error similar to "host for vpn address does not exist"
> > > > >
> > > > > What am I doing incorrectly?
> > > >
> > > > The error similar to that that I am thinking of would indicate that
> > > the
> > > > ip address of your client machine does not fall into the scheme laid
> > > out
> > > > in your pg_hba.conf. Most likely you need to add your home machines
> > ip
> > > > into the pg_hba.conf (or open up one of the existing entries to
> > > include
> > > > the machine your connecting from)
> > > >
> > > > HTH
> > > >
> > > > Robert Treat
> > >
> > > --
> > > Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
> > >
> > > ---------------------------(end of
> > broadcast)---------------------------
> > > TIP 4: Don't 'kill -9' the postmaster
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 7: don't forget to increase your free space map settings
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 10:48 Jim Seymour <jseymour@LinxNet.com>
0 siblings, 0 replies; 53+ messages in thread
From: jseymour@LinxNet.com @ 2004-05-26 10:48 UTC (permalink / raw)
To: pgsql-admin
>
> Hello,
>
> I believe I found my problem. The Cisco VPN client I use encrypts data
> at a 168 bit level. Postgres only supports up to 128 bit correct?
That's your VPN's end-to-end/network-to-network connectivity. It has
nothing to do with PostgreSQL at all.
(Note: Please do NOT copy me on replies. I do read the mailing
list.)
Jim
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 14:27 LSanchez@ameritrade.com
0 siblings, 2 replies; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-26 14:27 UTC (permalink / raw)
To: mike@thegodshalls.com; +Cc: xzilla@users.sourceforge.net; pgsql-admin
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.
-----Original Message-----
From: mike g [mailto:mike@thegodshalls.com]
Sent: Wednesday, May 26, 2004 12:51 AM
To: LSanchez@ameritrade.com
Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
Hello,
I believe I found my problem. The Cisco VPN client I use encrypts data
at a 168 bit level. Postgres only supports up to 128 bit correct?
Mike
On Tue, 2004-05-25 at 23:12, mike g wrote:
> Hmm....
>
> Looks like I am still in the same boat you are.
>
> I still cannot log into my db over a VPN connection using pgadminIII.
>
> Everytime I try and connect I get a "Server terminated connection
> unexpectedly error".
>
> I originally received the pg_hba.conf entry complaint as well but
after
> adding and restarting the system the above is all I get.
>
> I tried specifying pgadmin to prefer SSL connection, and changed
> pg_hba.conf entry to expect SSL from my VPN connection entry.
>
>
> On Tue, 2004-05-25 at 08:42, LSanchez@ameritrade.com wrote:
> > Thanks Mike!
> >
> > I already specified the IP address that was specified by my VPN
> > connection. I read through the docs and found nothing about anything
> > special with VPN connections.
> >
> > Regards,
> > - Lily Anne
> >
> > -----Original Message-----
> > From: Mike G [mailto:mike@thegodshalls.com]
> > Sent: Monday, May 24, 2004 10:23 PM
> > To: LSanchez@ameritrade.com
> > Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org
> > Subject: Re: [ADMIN] pg_hba.conf
> >
> > Your ip address range is probably different when connecting via a
VPN
> > rather than in the office. By default postgres will not allow
> > connections from other locations even if tcpip_socket is true
without
> > specifying an ip address range, database etc.
> >
> > Checkout the docs. There is a section on pg_hba.conf.
> >
> > Mike
> >
> > On Mon, May 24, 2004 at 01:02:12PM -0400, LSanchez@ameritrade.com
wrote:
> > > Yes I can ping the server if not connected via VPN.
> > >
> > > I'm using EMS PostgreSQL Manager, which works if not via VPN.
> > >
> > > Yes, postgresql.conf's tcpip_socket = true.
> > >
> > > The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113,
user
> > > postgres, database TEST.
> > >
> > > Thanks for your help!
> > >
> > > Regards,
> > > - Lily Anne
> > >
> > >
> > > -----Original Message-----
> > > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > > Sent: Friday, May 21, 2004 8:04 PM
> > > To: LSanchez@ameritrade.com
> > > Cc: pgsql-admin@postgresql.org
> > > Subject: Re: [ADMIN] pg_hba.conf
> > >
> > > can you ping the server that postgresql is living on? or maybe
your
> > > misrepresenting the error message... what program are you using
to
> > try
> > > and
> > > connect? can you verify that tcpip_sockets is turned on the
server?
> > > also, if
> > > it is a database problem there will be an exact error message
being
> > > reported
> > > in the logs of type FATAL, can you send us that?
> > >
> > > Robert Treat
> > >
> > > On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote:
> > > > Thanks Robert!
> > > >
> > > > I did that as well and still didn't work. Any other ideas?
> > > >
> > > > -----Original Message-----
> > > > From: Robert Treat [mailto:xzilla@users.sourceforge.net]
> > > > Sent: Friday, May 21, 2004 4:41 PM
> > > > To: LSanchez@ameritrade.com
> > > > Cc: pgsql-admin@postgresql.org
> > > > Subject: Re: [ADMIN] pg_hba.conf
> > > >
> > > > On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote:
> > > > > I'm trying to access our test postgreSQL server via VPN and
even
> > > >
> > > > though
> > > >
> > > > > I already setup the host for the vpn's ip address, I'm still
> > getting
> > > >
> > > > an
> > > >
> > > > > error similar to "host for vpn address does not exist"
> > > > >
> > > > > What am I doing incorrectly?
> > > >
> > > > The error similar to that that I am thinking of would indicate
that
> > > the
> > > > ip address of your client machine does not fall into the scheme
laid
> > > out
> > > > in your pg_hba.conf. Most likely you need to add your home
machines
> > ip
> > > > into the pg_hba.conf (or open up one of the existing entries to
> > > include
> > > > the machine your connecting from)
> > > >
> > > > HTH
> > > >
> > > > Robert Treat
> > >
> > > --
> > > Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
> > >
> > > ---------------------------(end of
> > broadcast)---------------------------
> > > TIP 4: Don't 'kill -9' the postmaster
> >
> > ---------------------------(end of
broadcast)---------------------------
> > TIP 7: don't forget to increase your free space map settings
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 14:55 Bruce Momjian <pgman@candle.pha.pa.us>
parent: LSanchez@ameritrade.com
1 sibling, 0 replies; 53+ messages in thread
From: Bruce Momjian @ 2004-05-26 14:55 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net; pgsql-admin
LSanchez@ameritrade.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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 15:25 LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-26 15:25 UTC (permalink / raw)
To: pgman@candle.pha.pa.us; +Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net; pgsql-admin
Thanks so much! :)
-----Original Message-----
From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
Sent: Wednesday, May 26, 2004 10:56 AM
To: LSanchez@ameritrade.com
Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
LSanchez@ameritrade.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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania
19073
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 15:29 Bruno Wolff III <bruno@wolff.to>
parent: LSanchez@ameritrade.com
1 sibling, 0 replies; 53+ messages in thread
From: Bruno Wolff III @ 2004-05-26 15:29 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net; pgsql-admin
On Wed, May 26, 2004 at 10:27:41 -0400,
LSanchez@ameritrade.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.
The client can use ssl. That supports 128 bit keys which is plenty.
Any adversary that has the resources to brute force a 128bit key has
the resources to do black bag jobs for a lower cost. If there are other
weaknesses besides brute force attacks, increasing the key size alone
isn't going to magicly make things better.
What kinds of threats are you trying to protect against? If you are using
an encrypted link already, using ssl isn't going to add much security.
Just allowing people to connect to the database directly is a significant
risk. It is made worse by letting people do it home where the machines
may not be safely operated by the users, which are not physically secured
and for which maitainance is harder (or not being done by the company).
If you are worried about people stealing hardware with information on it,
you should be considering better physical security, proper procedures
for destroying old media and consider using encrypted file systems.
If you are looking for ideas for how to hide information from authroized
users of a database while letting them use it for some things, Peter Wayner's
book Translucent Databases might be of some interest.
> -----Original Message-----
> From: mike g [mailto:mike@thegodshalls.com]
> Sent: Wednesday, May 26, 2004 12:51 AM
> To: LSanchez@ameritrade.com
> Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> Hello,
>
> I believe I found my problem. The Cisco VPN client I use encrypts data
> at a 168 bit level. Postgres only supports up to 128 bit correct?
>
> Mike
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 15:34 Jim Seymour <jseymour@linxnet.com>
0 siblings, 0 replies; 53+ messages in thread
From: jseymour@linxnet.com @ 2004-05-26 15:34 UTC (permalink / raw)
To: pgsql-admin
Note: Please do NOT Cc: me on replies to the mailing list. I read the
mailing list. One copy of your comments is sufficient. Thank you.
>
> 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.=20
As I told "mike g": pgsql's encryption has *nothing* to do with your
VPN's encryption. I'm running a sort of a VPN, using port-
forwarding over OpenSSH. In fact, from work just now...
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-26 19:02 Chris Browne <cbbrowne@acm.org>
parent: mike g <mike@thegodshalls.com>
0 siblings, 0 replies; 53+ messages in thread
From: Chris Browne @ 2004-05-26 19:02 UTC (permalink / raw)
To: pgsql-admin
mike@thegodshalls.com (mike g) writes:
> I believe I found my problem. The Cisco VPN client I use encrypts data
> at a 168 bit level. Postgres only supports up to 128 bit correct?
That ought to be entirely irrelevant, as your VPN client would encrypt
all data going across the network, encrypted or not. Indeed, if the
VPN is encrypting the data, it is redundant to have the database
server encrypt it an extra time.
That will just make things perform poorly.
And if you have some network configuration problem, adding in extra
layers of encryption is unlikely to make it easier to solve the
problem...
--
(reverse (concatenate 'string "gro.mca" "@" "enworbbc"))
http://cbbrowne.com/info/linux.html
Howe's Law:
Everyone has a scheme that will not work.
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-27 03:16 mike g <mike@thegodshalls.com>
parent: LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: mike g @ 2004-05-27 03:16 UTC (permalink / raw)
To: LSanchez@ameritrade.com; +Cc: 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@ameritrade.com wrote:
> Thanks so much! :)
>
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> Sent: Wednesday, May 26, 2004 10:56 AM
> To: LSanchez@ameritrade.com
> Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
> pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> LSanchez@ameritrade.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.
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-27 03:35 C. Bensend <benny@bennyvision.com>
parent: mike g <mike@thegodshalls.com>
0 siblings, 1 reply; 53+ messages in thread
From: C. Bensend @ 2004-05-27 03:35 UTC (permalink / raw)
To: mike@thegodshalls.com; +Cc: lsanchez@ameritrade.com; pgsql-admin
> 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.
Yes, when your subnet mask is set for a /24, that's correct.
Your first attempt above allowed connections for anything in the
10.15.0/24 subnet (which 10.15.13 is not a part of).
Benny
--
"Oh, the Jedis are going to feel this one!" -- Professor Farnsworth,
"Futurama"
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-27 13:35 Tom Lane <tgl@sss.pgh.pa.us>
parent: C. Bensend <benny@bennyvision.com>
0 siblings, 1 reply; 53+ messages in thread
From: Tom Lane @ 2004-05-27 13:35 UTC (permalink / raw)
To: C. Bensend <benny@bennyvision.com>; +Cc: mike@thegodshalls.com; lsanchez@ameritrade.com; pgsql-admin
"C. Bensend" <benny@bennyvision.com> writes:
>> 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:
> Yes, when your subnet mask is set for a /24, that's correct.
To expand a bit: the correct way of letting in a /16 would be
host all all 10.15.0.0 255.255.0.0 trust
In recent PG releases (7.4.*, not sure about 7.3) you could also write
host all all 10.15.0.0/16 trust
regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-27 13:37 LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-27 13:37 UTC (permalink / raw)
To: mike@thegodshalls.com; +Cc: pgsql-admin
Hi Mike,
That's exactly how I had mine setup all along:
host all all 10.29.15.0 255.255.255.0 trust
and it just doesn't work via VPN.
Thanks,
- Lily Anne
-----Original Message-----
From: mike g [mailto:mike@thegodshalls.com]
Sent: Wednesday, May 26, 2004 11:16 PM
To: LSanchez@ameritrade.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
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@ameritrade.com wrote:
> Thanks so much! :)
>
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> Sent: Wednesday, May 26, 2004 10:56 AM
> To: LSanchez@ameritrade.com
> Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
> pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> LSanchez@ameritrade.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.
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-27 14:02 Jim Seymour <jseymour@linxnet.com>
0 siblings, 0 replies; 53+ messages in thread
From: jseymour@linxnet.com @ 2004-05-27 14:02 UTC (permalink / raw)
To: pgsql-admin; +Cc: LSanchez@ameritrade.com
(Note: Please do not copy me individually on posts to the mailing
list. I do read the list and don't need two copies. Thanks.)
(Note2: I did Cc: this to LSanchez as she's yet to respond to any of
my prior comments, so I begin to suspect she's not getting/reading
the mailing list traffic?)
>
> Hi Mike,
>
> That's exactly how I had mine setup all along:
>
> host all all 10.29.15.0 255.255.255.0 trust
>
> and it just doesn't work via VPN.
Then I would suggest the server isn't seeing you coming from
10.29.15.0 through 10.29.15.255. Then again: There's been some kind
of bug (?) mentioned lately (only on [certain versions?] of Solaris?)
where "network netmask" doesn't appear to work properly. Try
changing the "10.29.15.0 255.255.255.0" to "10.29.15.0/24", if you
have a 7.4-series pgsql server, and see if that doesn't work.
Jim
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-27 14:11 Armstrong, Marc <marmstrong@danly.com>
0 siblings, 0 replies; 53+ messages in thread
From: Armstrong, Marc @ 2004-05-27 14:11 UTC (permalink / raw)
To: 'mike@thegodshalls.com' <mike@thegodshalls.com>; +Cc: pgsql-admin
Mike,
I think if you set it up like this it would have worked as well:
host all all 10.15.0.0 255.255.0.0 trust
Your netmask was telling it that the first three octets of the IP address
were significant.
Marc Armstrong - Webmaster - Danly IEM - 440-239-7607
marmstrong@danly.com - webmaster@danly.com
AIM: marmstro2 - Jabber: marmstro@amessage.de
-----Original Message-----
From: mike g [mailto:mike@thegodshalls.com]
Sent: Wednesday, May 26, 2004 11:16 PM
To: LSanchez@ameritrade.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hba.conf
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@ameritrade.com wrote:
> Thanks so much! :)
>
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> Sent: Wednesday, May 26, 2004 10:56 AM
> To: LSanchez@ameritrade.com
> Cc: mike@thegodshalls.com; xzilla@users.sourceforge.net;
> pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> LSanchez@ameritrade.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.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-27 14:12 LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-27 14:12 UTC (permalink / raw)
To: pgsql-admin
Hi Jim,
I apologize, but it seems that this is the first time that I received an
email from you, but I did receive some emails from others about this
issue, which I had been responding to. Or maybe, I'm not subscribed to
the mailing list? I'll check this out and fix it asap.
I will try what you suggested tonight, as soon as I get home.
Thanks so much for your help!
Regards,
- Lily Anne
-----Original Message-----
From: Jim Seymour [mailto:jseymour@linxnet.com]
Sent: Thursday, May 27, 2004 10:03 AM
To: pgsql-admin@postgresql.org
Cc: LSanchez@ameritrade.com
Subject: Re: [ADMIN] pg_hba.conf
(Note: Please do not copy me individually on posts to the mailing
list. I do read the list and don't need two copies. Thanks.)
(Note2: I did Cc: this to LSanchez as she's yet to respond to any of
my prior comments, so I begin to suspect she's not getting/reading
the mailing list traffic?)
>
> Hi Mike,
>
> That's exactly how I had mine setup all along:
>
> host all all 10.29.15.0 255.255.255.0 trust
>
> and it just doesn't work via VPN.
Then I would suggest the server isn't seeing you coming from
10.29.15.0 through 10.29.15.255. Then again: There's been some kind
of bug (?) mentioned lately (only on [certain versions?] of Solaris?)
where "network netmask" doesn't appear to work properly. Try
changing the "10.29.15.0 255.255.255.0" to "10.29.15.0/24", if you
have a 7.4-series pgsql server, and see if that doesn't work.
Jim
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-28 01:54 Mike G <mike@thegodshalls.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 53+ messages in thread
From: Mike G @ 2004-05-28 01:54 UTC (permalink / raw)
To: pgsql-admin
Thank you to all who replied with the additional info.
On Thu, May 27, 2004 at 09:35:06AM -0400, Tom Lane wrote:
> "C. Bensend" <benny@bennyvision.com> writes:
> >> 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:
>
> > Yes, when your subnet mask is set for a /24, that's correct.
>
> To expand a bit: the correct way of letting in a /16 would be
>
> host all all 10.15.0.0 255.255.0.0 trust
>
> In recent PG releases (7.4.*, not sure about 7.3) you could also write
>
> host all all 10.15.0.0/16 trust
>
> regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-28 14:52 LSanchez@ameritrade.com
0 siblings, 1 reply; 53+ messages in thread
From: LSanchez@ameritrade.com @ 2004-05-28 14:52 UTC (permalink / raw)
To: pgsql-admin
Jim said:
>>>
Try changing the "10.29.15.0 255.255.255.0" to "10.29.15.0/24", if
you
have a 7.4-series pgsql server, and see if that doesn't work.
>>>
IT WORKED! Thanks so much Jim! I'm happily connected from home today...
:)
-----Original Message-----
From: Sanchez, Lily
Sent: Thursday, May 27, 2004 10:12 AM
To: 'pgsql-admin@postgresql.org'
Subject: RE: [ADMIN] pg_hba.conf
Hi Jim,
I apologize, but it seems that this is the first time that I received an
email from you, but I did receive some emails from others about this
issue, which I had been responding to. Or maybe, I'm not subscribed to
the mailing list? I'll check this out and fix it asap.
I will try what you suggested tonight, as soon as I get home.
Thanks so much for your help!
Regards,
- Lily Anne
-----Original Message-----
From: Jim Seymour [mailto:jseymour@linxnet.com]
Sent: Thursday, May 27, 2004 10:03 AM
To: pgsql-admin@postgresql.org
Cc: LSanchez@ameritrade.com
Subject: Re: [ADMIN] pg_hba.conf
(Note: Please do not copy me individually on posts to the mailing
list. I do read the list and don't need two copies. Thanks.)
(Note2: I did Cc: this to LSanchez as she's yet to respond to any of
my prior comments, so I begin to suspect she's not getting/reading
the mailing list traffic?)
>
> Hi Mike,
>
> That's exactly how I had mine setup all along:
>
> host all all 10.29.15.0 255.255.255.0 trust
>
> and it just doesn't work via VPN.
Then I would suggest the server isn't seeing you coming from
10.29.15.0 through 10.29.15.255. Then again: There's been some kind
of bug (?) mentioned lately (only on [certain versions?] of Solaris?)
where "network netmask" doesn't appear to work properly. Try
changing the "10.29.15.0 255.255.255.0" to "10.29.15.0/24", if you
have a 7.4-series pgsql server, and see if that doesn't work.
Jim
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2004-05-28 22:00 Jim Seymour <jseymour@linxnet.com>
parent: LSanchez@ameritrade.com
0 siblings, 0 replies; 53+ messages in thread
From: jseymour@linxnet.com @ 2004-05-28 22:00 UTC (permalink / raw)
To: pgsql-admin; +Cc: LSanchez@ameritrade.com
<LSanchez@ameritrade.com> wrote:
>
> Jim said:
> >>>
> Try changing the "10.29.15.0 255.255.255.0" to "10.29.15.0/24", if
> you
> have a 7.4-series pgsql server, and see if that doesn't work.
> >>>
>
> IT WORKED! Thanks so much Jim! I'm happily connected from home today...
> :)
It was a long shot, but it worked. Very good :).
I'm curious, Lily, could you share with us just what operating system
and version/release the PostgreSQL server is running on? And what
version of PostgreSQL is running on that server? Reason I ask is that
the solution I presented has so far only been associated with some (?)
versions of pgsql running on some (?) versions of Sun Solaris.
(Note: I'm Cc'ing you again as last time you mentioned you weren't
getting the mailing list itself.)
Jim
^ permalink raw reply [nested|flat] 53+ messages in thread
* pg_hba.conf
@ 2005-02-22 11:56 Dick Davies <rasputnik@hellooperator.net>
0 siblings, 1 reply; 53+ messages in thread
From: Dick Davies @ 2005-02-22 11:56 UTC (permalink / raw)
To: pgsql-admin
Just needed clarification on how pg_hba.conf operates.
Does a specific host take precedence over a more general network setting?
The local socket is only accessible to a certain group, but I don't want
the overhead of SSL for loopback connections. If I connect to the server
from the local machine, the connections show up as (eg) 10.2.3.4, the NIC
ip.
I was hoping the more specific 'host' entry would take entry over the universal
'hostssl' entry, but it does'nt seem to...
I have this:
root@eris:postgresql80-server$ cat /opt/pgsql/data/pg_hba.conf
# TYPE DATABASE USER IP-ADDRESS METHOD
local all all trust
host all all 10.2.3.4/32 md5
hostssl all all 0.0.0.0/0 md5
Is there a way to say 'all IP traffic should be encrypted except one IP' that
I'm missing?
I know I could just add the local process into the dba group, but the app doesn't
reconnect if the socket goes away on a db restart, so that's not ideal...
--
'That question was less stupid; though you asked it in a profoundly stupid way.'
-- Prof. Farnsworth
Rasputin :: Jack of All Trades - Master of Nuns
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2005-02-22 12:21 KÖPFERL Robert <robert.koepferl@sonorys.at>
0 siblings, 1 reply; 53+ messages in thread
From: KÖPFERL Robert @ 2005-02-22 12:21 UTC (permalink / raw)
To: pgsql-admin
According to the excelent doc, the _first_ matching entry will be used.
C:\> -----Original Message-----
C:\> From: Dick Davies [mailto:rasputnik@hellooperator.net]
C:\> Sent: Dienstag, 22. Februar 2005 12:57
C:\> To: PostgreSQL Admin
C:\> Subject: [ADMIN] pg_hba.conf
C:\>
C:\>
C:\>
C:\> Just needed clarification on how pg_hba.conf operates.
C:\> Does a specific host take precedence over a more general
C:\> network setting?
C:\>
C:\> The local socket is only accessible to a certain group,
C:\> but I don't want
C:\> the overhead of SSL for loopback connections. If I connect
C:\> to the server
C:\> from the local machine, the connections show up as (eg)
C:\> 10.2.3.4, the NIC
C:\> ip.
C:\>
C:\> I was hoping the more specific 'host' entry would take
C:\> entry over the universal
C:\> 'hostssl' entry, but it does'nt seem to...
C:\>
C:\> I have this:
C:\>
C:\> root@eris:postgresql80-server$ cat /opt/pgsql/data/pg_hba.conf
C:\> # TYPE DATABASE USER IP-ADDRESS METHOD
C:\> local all all trust
C:\> host all all 10.2.3.4/32 md5
C:\> hostssl all all 0.0.0.0/0 md5
C:\>
C:\> Is there a way to say 'all IP traffic should be encrypted
C:\> except one IP' that
C:\> I'm missing?
C:\>
C:\> I know I could just add the local process into the dba
C:\> group, but the app doesn't
C:\> reconnect if the socket goes away on a db restart, so
C:\> that's not ideal...
C:\>
C:\>
C:\> --
C:\> 'That question was less stupid; though you asked it in a
C:\> profoundly stupid way.'
C:\> -- Prof. Farnsworth
C:\> Rasputin :: Jack of All Trades - Master of Nuns
C:\>
C:\> ---------------------------(end of
C:\> broadcast)---------------------------
C:\> TIP 7: don't forget to increase your free space map settings
C:\>
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2005-02-22 13:26 Dick Davies <rasputnik@hellooperator.net>
parent: KÖPFERL Robert <robert.koepferl@sonorys.at>
0 siblings, 1 reply; 53+ messages in thread
From: Dick Davies @ 2005-02-22 13:26 UTC (permalink / raw)
To: pgsql-admin
* K?PFERL Robert <robert.koepferl@sonorys.at> [0228 12:28]:
> According to the excelent doc, the _first_ matching entry will be used.
If that were true, the below would work, surely?
> C:\> I have this:
> C:\>
> C:\> root@eris:postgresql80-server$ cat /opt/pgsql/data/pg_hba.conf
> C:\> # TYPE DATABASE USER IP-ADDRESS METHOD
> C:\> local all all trust
> C:\> host all all 10.2.3.4/32 md5
> C:\> hostssl all all 0.0.0.0/0 md5
--
'Interesting. No, wait, the other thing - Tedious.'
-- Bender
Rasputin :: Jack of All Trades - Master of Nuns
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2005-02-22 13:48 Donald Fraser <postgres@kiwi-fraser.net>
parent: Dick Davies <rasputnik@hellooperator.net>
0 siblings, 1 reply; 53+ messages in thread
From: Donald Fraser @ 2005-02-22 13:48 UTC (permalink / raw)
To: pgsql-admin
If postgres has ssl enabled then it will by default negotiate to use ssl,
regardless of the host or hostssl settings in pg_hba. Your client software
needs to refuse ssl connections then it will fall back to a non-ssl
connection so long as there exists a host setting in pg_hba. The hostssl
setting in pg_hba means that it must use ssl to connect, where as the host
setting in pg_hba can mean either or, depending on your client.
What client software are you using?
Regards
Donald Fraser
----- Original Message -----
From: "Dick Davies" <rasputnik@hellooperator.net>
To: "PostgreSQL Admin" <pgsql-admin@postgresql.org>
Sent: Tuesday, February 22, 2005 1:26 PM
Subject: Re: [ADMIN] pg_hba.conf
> * K?PFERL Robert <robert.koepferl@sonorys.at> [0228 12:28]:
> > According to the excelent doc, the _first_ matching entry will be used.
>
> If that were true, the below would work, surely?
>
> > C:\> I have this:
> > C:\>
> > C:\> root@eris:postgresql80-server$ cat /opt/pgsql/data/pg_hba.conf
> > C:\> # TYPE DATABASE USER IP-ADDRESS METHOD
> > C:\> local all all trust
> > C:\> host all all 10.2.3.4/32 md5
> > C:\> hostssl all all 0.0.0.0/0 md5
>
> --
> 'Interesting. No, wait, the other thing - Tedious.'
> -- Bender
> Rasputin :: Jack of All Trades - Master of Nuns
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2005-02-22 14:25 Dick Davies <rasputnik@hellooperator.net>
parent: Donald Fraser <postgres@kiwi-fraser.net>
0 siblings, 0 replies; 53+ messages in thread
From: Dick Davies @ 2005-02-22 14:25 UTC (permalink / raw)
To: Donald Fraser <postgres@kiwi-fraser.net>; +Cc: pgsql-admin
* Donald Fraser <postgres@kiwi-fraser.net> [0257 13:57]:
> If postgres has ssl enabled then it will by default negotiate to use ssl,
> regardless of the host or hostssl settings in pg_hba. Your client software
> needs to refuse ssl connections then it will fall back to a non-ssl
> connection so long as there exists a host setting in pg_hba. The hostssl
> setting in pg_hba means that it must use ssl to connect, where as the host
> setting in pg_hba can mean either or, depending on your client.
>
> What client software are you using?
psql and ignorance :)- though it'll be ruby-postgres for the webapp.
Thanks for the explanation.
--
'This must be Thursday. I never could get the hang of Thursdays.'
-- Arthur Dent
Rasputin :: Jack of All Trades - Master of Nuns
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2005-02-22 14:47 Bruno Wolff III <bruno@wolff.to>
parent: Dick Davies <rasputnik@hellooperator.net>
0 siblings, 1 reply; 53+ messages in thread
From: Bruno Wolff III @ 2005-02-22 14:47 UTC (permalink / raw)
To: Dick Davies <rasputnik@hellooperator.net>; +Cc: pgsql-admin
On Tue, Feb 22, 2005 at 11:56:41 +0000,
Dick Davies <rasputnik@hellooperator.net> wrote:
>
> Just needed clarification on how pg_hba.conf operates.
> Does a specific host take precedence over a more general network setting?
No. The first line that matches the triple connection type, database name
and user name is the one that is used. Typically you can get what you
want by using the narrower rule first.
> The local socket is only accessible to a certain group, but I don't want
> the overhead of SSL for loopback connections. If I connect to the server
> from the local machine, the connections show up as (eg) 10.2.3.4, the NIC
> ip.
>
> I was hoping the more specific 'host' entry would take entry over the universal
> 'hostssl' entry, but it does'nt seem to...
The host entry is the one that applies. But the host entry will allow either
ssl or nonssl, so it doesn't do what you want without cooperation from the
connecting client. You can use hostnossl to match without allowing ssl.
You will also want to use a hostssl line with 'reject' authentication
to keep the later rule from matching. I am not sure if all of the normal
clients will fallback after trying ssl to not using ssl. That should be
pretty easy to test though.
>
> I have this:
>
> root@eris:postgresql80-server$ cat /opt/pgsql/data/pg_hba.conf
> # TYPE DATABASE USER IP-ADDRESS METHOD
> local all all trust
> host all all 10.2.3.4/32 md5
> hostssl all all 0.0.0.0/0 md5
>
> Is there a way to say 'all IP traffic should be encrypted except one IP' that
> I'm missing?
>
> I know I could just add the local process into the dba group, but the app doesn't
> reconnect if the socket goes away on a db restart, so that's not ideal...
>
>
> --
> 'That question was less stupid; though you asked it in a profoundly stupid way.'
> -- Prof. Farnsworth
> Rasputin :: Jack of All Trades - Master of Nuns
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2005-02-22 15:18 Tom Lane <tgl@sss.pgh.pa.us>
parent: Bruno Wolff III <bruno@wolff.to>
0 siblings, 1 reply; 53+ messages in thread
From: Tom Lane @ 2005-02-22 15:18 UTC (permalink / raw)
To: Bruno Wolff III <bruno@wolff.to>; +Cc: Dick Davies <rasputnik@hellooperator.net>; pgsql-admin
Bruno Wolff III <bruno@wolff.to> writes:
> The host entry is the one that applies. But the host entry will allow either
> ssl or nonssl, so it doesn't do what you want without cooperation from the
> connecting client. You can use hostnossl to match without allowing ssl.
> You will also want to use a hostssl line with 'reject' authentication
> to keep the later rule from matching. I am not sure if all of the normal
> clients will fallback after trying ssl to not using ssl. That should be
> pretty easy to test though.
Perhaps easier would be to set "PGSSLMODE=allow" (or even "disable") in
the client environment. This will work for libpq-based clients; there
may be something equivalent if you are using other software.
The important point here is that it's the client's choice whether to try
an SSL connection first or not, and libpq defaults to trying SSL first.
So unless you set up pg_hba.conf to actively reject SSL-based
connections, that's what you're going to get.
Also: why aren't you just using a Unix socket? We never do SSL over
Unix sockets.
regards, tom lane
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2005-02-22 16:14 Dick Davies <rasputnik@hellooperator.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 53+ messages in thread
From: Dick Davies @ 2005-02-22 16:14 UTC (permalink / raw)
To: pgsql-admin
* Tom Lane <tgl@sss.pgh.pa.us> [0218 15:18]:
> Perhaps easier would be to set "PGSSLMODE=allow" (or even "disable") in
> the client environment. This will work for libpq-based clients; there
> may be something equivalent if you are using other software.
Thanks Tom, I'll give that a go.
> Also: why aren't you just using a Unix socket? We never do SSL over
> Unix sockets.
As I said, it's set to 'trust' and restricted to a local group.
Also, the deletion/rebuilding of the socket causes the application to
lose the db connection, hopefully it will be more forgiving of a server
bounce over IP.
--
'Oh, wait you're serious. Let me laugh even harder.'
-- Bender
Rasputin :: Jack of All Trades - Master of Nuns
^ permalink raw reply [nested|flat] 53+ messages in thread
* pg_hba.conf
@ 2006-02-21 19:39 Gowri Sivaraman <gsivaraman@magnasync.com>
0 siblings, 1 reply; 53+ messages in thread
From: Gowri Sivaraman @ 2006-02-21 19:39 UTC (permalink / raw)
To: pgsql-admin
Hi,
I am having problems with my connectivity for any of the users other
than the post gres. Let me elaborate on the situation
I am using OSX and i have changed the pg_hba.conf file to reflect
ident_authentication. I have attached my pg_hba.conf file. When i try
connecting as a user i get the following error
Gowri-Sivaraman:~ gowri$ psql -h localhost gen3logger
psql: FATAL: Ident authentication failed for user "gowri"
Even when i have given the user gowri trust authorization, it is not
working. For some reason, it is recognizing local . when i connect
using the host it is working. Can anybody let me know if i am missing
something here
Gowri-Sivaraman:~ gowri$ psql -h 127.0.0.1 -U gowri template1
Welcome to psql 8.1.3, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
template1=>
Thanks
Gowri
Attachments:
pg_hba.conf (application/octet-stream, 8.3K) download
^ permalink raw reply [nested|flat] 53+ messages in thread
* Re: pg_hba.conf
@ 2006-03-01 10:02 Andy Shellam <andy@andycc.net>
parent: Gowri Sivaraman <gsivaraman@magnasync.com>
0 siblings, 0 replies; 53+ messages in thread
From: Andy Shellam @ 2006-03-01 10:02 UTC (permalink / raw)
To: gsivaraman@magnasync.com; +Cc: pgsql-admin
Have you also changed your pg_ident.conf to map the user gowri to a
database user, and does that database user exist in pgSQL?
By default 127.0.0.1 is set up as trust authentication, so if you
haven't changed this, it will always let you through no matter what
username/password you give.
Andy
Gowri Sivaraman wrote:
> Hi,
> I am having problems with my connectivity for any of the users other
> than the post gres. Let me elaborate on the situation
>
>
> I am using OSX and i have changed the pg_hba.conf file to reflect
> ident_authentication. I have attached my pg_hba.conf file. When i try
> connecting as a user i get the following error
>
>
> Gowri-Sivaraman:~ gowri$ psql -h localhost gen3logger
> psql: FATAL: Ident authentication failed for user "gowri"
>
>
> Even when i have given the user gowri trust authorization, it is not
> working. For some reason, it is recognizing local . when i connect
> using the host it is working. Can anybody let me know if i am missing
> something here
>
>
> Gowri-Sivaraman:~ gowri$ psql -h 127.0.0.1 -U gowri template1
> Welcome to psql 8.1.3, the PostgreSQL interactive terminal.
>
> Type: \copyright for distribution terms
> \h for help with SQL commands
> \? for help with psql commands
> \g or terminate with semicolon to execute query
> \q to quit
>
> SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
>
> template1=>
>
>
>
>
> !DSPAM:14,440507c549411563562004!
>
>
>
>
> Thanks
> Gowri
>
>
> !DSPAM:14,440507c549411563562004!
> ------------------------------------------------------------------------
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
>
> !DSPAM:14,440507c549411563562004!
>
^ permalink raw reply [nested|flat] 53+ messages in thread
end of thread, other threads:[~2006-03-01 10:02 UTC | newest]
Thread overview: 53+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-11-01 11:51 pg_hba.conf Eduardo Kotujansky <eduardo@complex.com.br>
2000-11-01 13:43 ` Giovanni Serrato Castillo <gserrato@sager.telecom-co.net>
2003-02-27 19:59 pg_hba.conf Sidar Lopez Cruz <sidarlopez@hotmail.com>
2003-02-27 22:50 ` Robert Treat <xzilla@users.sourceforge.net>
2003-02-28 20:16 ` Ed L. <pgsql@bluepolka.net>
2003-10-16 04:40 pg_hba.conf Ganesan Kanavathy <ganesh@magnusquest.com>
2003-10-16 06:44 pg_hba.conf Ashok Chauhan <ashok@kalculate.com>
2003-10-16 06:50 ` Will LaShell <will@lashell.net>
2003-10-16 14:43 ` Christopher Browne <cbbrowne@libertyrms.info>
2004-05-20 23:52 pg_hba.conf LSanchez@ameritrade.com
2004-05-21 20:40 ` Robert Treat <xzilla@users.sourceforge.net>
2004-05-21 21:01 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-22 00:04 ` Robert Treat <xzilla@users.sourceforge.net>
2004-05-24 17:02 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-25 02:23 ` Mike G <mike@thegodshalls.com>
2004-05-25 13:42 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-25 14:50 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-05-25 20:33 ` Jim Seymour <jseymour@LinxNet.com>
2004-05-26 04:12 ` mike g <mike@thegodshalls.com>
2004-05-26 04:51 ` mike g <mike@thegodshalls.com>
2004-05-26 19:02 ` Chris Browne <cbbrowne@acm.org>
2004-05-25 14:50 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-25 17:02 ` Robert Treat <xzilla@users.sourceforge.net>
2004-05-25 17:13 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-25 18:51 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-05-25 18:54 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-25 19:17 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-26 10:48 Re: pg_hba.conf Jim Seymour <jseymour@LinxNet.com>
2004-05-26 14:27 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-26 14:55 ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-05-26 15:29 ` Bruno Wolff III <bruno@wolff.to>
2004-05-26 15:25 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-27 03:16 ` mike g <mike@thegodshalls.com>
2004-05-27 03:35 ` C. Bensend <benny@bennyvision.com>
2004-05-27 13:35 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-05-28 01:54 ` Mike G <mike@thegodshalls.com>
2004-05-26 15:34 Re: pg_hba.conf Jim Seymour <jseymour@linxnet.com>
2004-05-27 13:37 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-27 14:02 Re: pg_hba.conf Jim Seymour <jseymour@linxnet.com>
2004-05-27 14:11 Re: pg_hba.conf Armstrong, Marc <marmstrong@danly.com>
2004-05-27 14:12 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-28 14:52 Re: pg_hba.conf LSanchez@ameritrade.com
2004-05-28 22:00 ` Jim Seymour <jseymour@linxnet.com>
2005-02-22 11:56 pg_hba.conf Dick Davies <rasputnik@hellooperator.net>
2005-02-22 14:47 ` Bruno Wolff III <bruno@wolff.to>
2005-02-22 15:18 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-02-22 16:14 ` Dick Davies <rasputnik@hellooperator.net>
2005-02-22 12:21 Re: pg_hba.conf KÖPFERL Robert <robert.koepferl@sonorys.at>
2005-02-22 13:26 ` Dick Davies <rasputnik@hellooperator.net>
2005-02-22 13:48 ` Donald Fraser <postgres@kiwi-fraser.net>
2005-02-22 14:25 ` Dick Davies <rasputnik@hellooperator.net>
2006-02-21 19:39 pg_hba.conf Gowri Sivaraman <gsivaraman@magnasync.com>
2006-03-01 10:02 ` Andy Shellam <andy@andycc.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox