From: | Alexandre Lollini <alex-admin(at)espacelollini(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Connecting to Postgres from LAN |
Date: | 2005-05-31 18:17:09 |
Message-ID: | BEC276C5.18FBA%alex-admin@espacelollini.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
on 30/05/05 20:47, Andrus <noeetasoftspam(at)online(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Snyder | 2005-05-31 18:20:21 | postgreSQL 7.3.8, pg_dump not able to find large object |
Previous Message | Marc G. Fournier | 2005-05-31 17:45:56 | Major flood of mail to lists ... |