Hi!

Thanks for the hint with the .pgpass. This solution works for me, but isn't
this the same like editing the pg_hba.conf like this:

host    all         all         127.0.0.1         255.255.255.255   md5
host    all         all         192.168.1.225     255.255.255.255   trust
host    all         all         192.168.1.223     255.255.255.255   trust

That means that all postgres servers that "participate" in the replication
have to be in there (here 223 y 225).

Does anyone of you see a security hole? I do not. The postgres web interface
connects to "localhost"...

Many thanks!

Sebastian


----- Original Message ----- 
From: "Christopher Browne" <cbbrowne at ca.afilias.info>
To: "Sebastian K?hner" <skuehner at veraza.com>
Cc: <slony1-general at gborg.postgresql.org>
Sent: Wednesday, September 07, 2005 4:12 PM
Subject: Re: [Slony1-general] Compile


> Sebastian K?hner wrote:
>
> >Hello,
> >
> >I created a cluster successfully now.
> >
> >On starting slone I get the error:
> >
> >2005-09-07 14:55:02 ART ERROR  slon_connectdb:
PQconnectdb("dbname=contact
> >host=localhost user=postgres") failed - fe_sendauth: no password supplied
> >
> >I have password protection on my postgresql servers (I use a
web-interface
> >to connect to the database, so it's necesary to evite that everyone can
> >login with localhost). Is there any way to setup the password with slony?
> >
> >Thanks!
> >
> >Sebastian
> >
> >
> >
> Slony-I is a "plain, ordinary" libpq-linked application, so you can use
> .pgpass to manage the passwords.
>
> Here's the .pgpass documentation:
> <http://www.postgresql.org/docs/8.0/interactive/libpq-pgpass.html>
>
> "Best practice" is indeed to use .pgpass; that means the passwords stay
> in one place rather than being strewn across all kinds of scripts
> everywhere in the environment.
>