From: Peter Eisentraut <peter_e@gmx.net>
To: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Security with V9.3.3 standby servers
Date: Fri, 27 Feb 2015 14:02:45 -0500
Message-ID: <54F0BF55.6020002@gmx.net> (raw)
In-Reply-To: <54EF46B7.3000809@gmail.com>
References: <54EF46B7.3000809@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On 2/26/15 11:15 AM, 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?
You can put the password in the a .pgpass file. Not sure if that counts
as a "script".
Or you can do away with passwords and authenticate using SSL client
certificates.
--
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: peter_e@gmx.net, jayknowsunix@gmail.com
Subject: Re: Security with V9.3.3 standby servers
In-Reply-To: <54F0BF55.6020002@gmx.net>
* 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