Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YR2hp-000864-O7 for pgsql-admin@arkaria.postgresql.org; Thu, 26 Feb 2015 17:58:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YR2hp-0003A5-6w for pgsql-admin@arkaria.postgresql.org; Thu, 26 Feb 2015 17:58:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YR2ho-00039k-GP for pgsql-admin@postgresql.org; Thu, 26 Feb 2015 17:58:36 +0000 Received: from mx.htip.com.br ([200.143.182.12] helo=mail.htip.com.br) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YR2hj-0007vN-FQ for pgsql-admin@postgresql.org; Thu, 26 Feb 2015 17:58:34 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.htip.com.br (Postfix) with ESMTP id EA33A50B3D3 for ; Thu, 26 Feb 2015 14:58:21 -0300 (BRT) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at htip.com.br Received: from mail.htip.com.br ([127.0.0.1]) by localhost (mail.htip.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEJzkMh-rLyh for ; Thu, 26 Feb 2015 14:58:21 -0300 (BRT) Received: from www.htip.com.br (localhost [127.0.0.1]) by mail.htip.com.br (Postfix) with ESMTP id C479B50B2F1 for ; Thu, 26 Feb 2015 14:58:21 -0300 (BRT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 26 Feb 2015 14:58:21 -0300 From: luis.sa@htip.com.br To: Subject: Re: Security with V9.3.3 standby servers In-Reply-To: <54EF46B7.3000809@gmail.com> References: <54EF46B7.3000809@gmail.com> Message-ID: X-Sender: luis.sa@htip.com.br User-Agent: RoundCube Webmail/0.5.3 X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin