Re: Security with V9.3.3 standby servers - Mailing list pgsql-admin

From luis.sa@htip.com.br
Subject Re: Security with V9.3.3 standby servers
Date
Msg-id f33c0befa4af7ab4a07a647c3796378e@htip.com.br
Whole thread Raw
In response to Security with V9.3.3 standby servers  (John Scalia <jayknowsunix@gmail.com>)
List pgsql-admin
On Thu, 26 Feb 2015 11:15:51 -0500, John Scalia wrote:
> Hi all,
>
> 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?
>
> Thx,
> Jay


Yes. Use ssh key to create a fingerprint.

Ex. "ssh-keygen" command to generate a fingerprint. And "ssh-copy-id
postgres@slave" and  "ssh-copy-id user@master" to copy the key to alow
both machines communicated over ssh.


pgsql-admin by date:

Previous
From: John Scalia
Date:
Subject: Security with V9.3.3 standby servers
Next
From: luis.sa@htip.com.br
Date:
Subject: Re: Security with V9.3.3 standby servers