From: John Scalia <jayknowsunix@gmail.com>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Security with V9.3.3 standby servers
Date: Thu, 26 Feb 2015 21:40:16 -0500
Message-ID: <54EFD910.5020501@gmail.com> (raw)
In-Reply-To: <2645DF43-00E0-4AEB-B02F-DD8AE703528A@elevated-dev.com>
References: <54EF46B7.3000809@gmail.com>
<2645DF43-00E0-4AEB-B02F-DD8AE703528A@elevated-dev.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Ahhh, I hadn't considered that. Thanks, I think I'll try that tomorrow morning.
On 2/26/2015 4:57 PM, Scott Ribe wrote:
> On Feb 26, 2015, at 9:15 AM, John Scalia <jayknowsunix@gmail.com> 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?
> I have replica standbys that are firewalled from the primary. The primary establishes a reverse SSH tunnel to the replica, then the replica is configured as for a local connection on-server at the primary, just using UNIX identity.
>
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jayknowsunix@gmail.com, scott_ribe@elevated-dev.com
Subject: Re: Security with V9.3.3 standby servers
In-Reply-To: <54EFD910.5020501@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox