- Original Message -
From: "Serge Dubrouski"
To:
Sent: Sunday, September 20, 2009 9:22 PM
Subject: Re: [Pacemaker] postgresql RA problem [SOLVED]
Ok. I reviewed what was changed and I'm afraid that these changes are
no good. Using PGPASSWORD variable isn't reco
- Original Message -
From: "Serge Dubrouski"
To:
Sent: Sunday, September 20, 2009 9:22 PM
Subject: Re: [Pacemaker] postgresql RA problem [SOLVED]
Ok. I reviewed what was changed and I'm afraid that these changes are
no good. Using PGPASSWORD variable isn't reco
Ok. I reviewed what was changed and I'm afraid that these changes are
no good. Using PGPASSWORD variable isn't recommended because it's
considered as insecure. Putting DBA password into pacemaker
configuration brings even more security issues. .pgpass file shall be
used instead when password authen
Can you provide your change as a diff patch?
On Sat, Sep 19, 2009 at 11:22 PM, E-Blokos wrote:
> For whos are interested to have more password security with Postgresql
> until now the RA didn't work if db user in pg_hba.conf was set on other than
> "trust",
> otherwise psql command always ask pa
- Original Message -
From: E-Blokos
To: pacema...@clusterlabs.org
Sent: Sunday, September 20, 2009 1:22 AM
Subject: postgresql RA problem [SOLVED]
For whos are interested to have more password security with Postgresql
until now the RA didn't work if db user in pg_hba.con
For whos are interested to have more password security with Postgresql
until now the RA didn't work if db user in pg_hba.conf was set on other than
"trust",
otherwise psql command always ask password prompt, which break the RA script.
So I updated the PGSQL RA to use pgsql with more security.
Re
