Connecting to Postgres from LAN

Started by Andrusalmost 21 years ago3 messagesgeneral
Jump to latest
#1Andrus
noeetasoftspam@online.ee

I installed Postgres 8 to Windows XP and added a line

host all all 168.179.0.1/32 trust

to pg_hba.conf file

When connection from LAN to the Postgres with user name postgres I got error

no pg_hba.conf entry for host "168.179.0.10", user "postgres", database
"mydb", SSL off

How to enable connection from LAN ?

Andrus

#2John Gray
jgray@azuli.co.uk
In reply to: Andrus (#1)
Re: Connecting to Postgres from LAN

On Mon, 30 May 2005 21:47:43 +0300, Andrus wrote:

I installed Postgres 8 to Windows XP and added a line

host all all 168.179.0.1/32 trust

I think you should probably make that 168.179.0.0/24 - the /32 means that
only the IP address 168.179.0.1 is covered by that line, so the pattern
does not match.

Regards

John Gray

#3Alexandre Lollini
alex-admin@espacelollini.com
In reply to: Andrus (#1)
Re: Connecting to Postgres from LAN

on 30/05/05 20:47, Andrus <noeetasoftspam@online.ee> wrote:

I installed Postgres 8 to Windows XP and added a line

host all all 168.179.0.1/32 trust

to pg_hba.conf file

When connection from LAN to the Postgres with user name postgres I got error

no pg_hba.conf entry for host "168.179.0.10", user "postgres", database
"mydb", SSL off

How to enable connection from LAN ?

Andrus

The solution is to edit the postgresql.conf file
And then enable LAN connections.

But before doing so, I urge you :

Your line in pg_hba.conf as is is EXTREMELY INSECURE
I suggest to be more tight than "all" and "trust"

Use a comma separated list of users (exclude postgres)
Use a comma separated list of databases (excluding templates and pg_)

Use "password" instead of "trust", at least.

So create some users with limited grants, with a password, even if these are
script users.

No network can be trusted.

User postgres is (and should stay) the only one user capable of DROP
DATABASE x

I strongly recomment not to use user postgres for runtime remote
connections.