Re: Security with V9.3.3 standby servers

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "John Scalia *EXTERN*" <jayknowsunix(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Security with V9.3.3 standby servers
Date: 2015-02-27 10:33:44
Message-ID: A737B7A37273E048B164557ADEF4A58B365A0E16@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

John Scalia wrote:
> An edict has been handed down here from on high that no script shall ever contain any password in
> cleartext for any reason. Well this is problem with a streaming replication
> standby server's recovery.conf file as the line primary_conninfo = contains said replication user's
> password for that connection. Is there any sort of plan to allow this to be md5
> or some such encoded? Or what else could I do in this case?

Well, I would consider "trust" authentication.

If you restrict it to a single IP address, I don't think it is less secure
than having your password lying around on another computer.

Yours,
Laurenz Albe

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Sergey Shchukin 2015-02-27 11:11:14 Re: Re: [pgadmin-support] Issue with a hanging apply process on the replica db after vacuum works on primary
Previous Message Jim Nasby 2015-02-27 08:52:34 Re: Re: [pgadmin-support] Issue with a hanging apply process on the replica db after vacuum works on primary