Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1idDbw-0000PW-2W for pgsql-admin@arkaria.postgresql.org; Fri, 06 Dec 2019 13:25:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1idDbu-0006pD-QB for pgsql-admin@arkaria.postgresql.org; Fri, 06 Dec 2019 13:25:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1idDbu-0006p6-EI for pgsql-admin@lists.postgresql.org; Fri, 06 Dec 2019 13:25:30 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1idDbs-0004Vk-7K for pgsql-admin@postgresql.org; Fri, 06 Dec 2019 13:25:30 +0000 Received: by mail-wm1-x329.google.com with SMTP id p17so7325559wmi.3 for ; Fri, 06 Dec 2019 05:25:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=d8xSInBYkVvpZ4hZFUFYL3uoOmNe/YiSnJaeKJRs6Jw=; b=WmriV9lYaIzPDv+6n5m7AHVj1Aekuu8k+ob9SFcOiJdpATp0QXXWd1d77NTGlQ2F8j aCXpSAKBETaEuEG0aTb9Ap4432t+aPfh+dO+tcfzWHZrOhwcA2mfPx04zwB9froJYr6F Q9+dIXqb4QSZ3F6Cq4/tMD33PgOD4MjtREM9K0lbDCBDw2d8p1xdtwEMaIiPDKLUNNbq cUhasm3I1Ozyz0QvJq5/4CsjJyYTkBa26Sh5EqaYNbAf0O78Qx5EhFXzRa7EZyoBKtwG D3dhLSKDSi44c91PdJXW/kgrBRn2JhyjbYsyDSRbfBD35ja0bdutIxjp/0+7lg1BQKni 2BSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=d8xSInBYkVvpZ4hZFUFYL3uoOmNe/YiSnJaeKJRs6Jw=; b=dgG9N7Ig3Xxrj9u0+q97PNTMb8BLB9UxoVZ5R/hLt0EewR43R0s+xlgu/kP6H5UlCb 3rTjrzDgX+885+lGITyM0Fd4vL05Be/LaBwcpvF4MK/xKPdeCYbGhwfpmC4ISwV4w+mc x26n+KWRYdIKmZ0lm1YWNyDyWcfRot9hjji6lzH7l6AUmC8hQnEPrGbofDXG2W1b4yVz zWSDEG+Sy0DpP/2Zb76awhJAQCF0Z9xSHK3ox+qHutp8qqGFp0y9DvY+sND9CuVYt0WG 4BAgFCEV8ADbKTA96nGSEejkFyP0vDxMhHOW+o4czjN9nmIJaa/YUW7MNX+4Alwon7SM P72w== X-Gm-Message-State: APjAAAUwjRTvs3LAaUUA/AO3rjDFJv085GbF6KT4G8FfhzKlOV/bHtb7 ZzvvwqMlJTd5lGxJnu+MCXymc68= X-Google-Smtp-Source: APXvYqwLyGEvI2RDhGDJOvbxJcblCdOjYZlelwa7iqx0gejXn3dVjnO5LwV+/2FNgI4UlQvJVmukdw== X-Received: by 2002:a7b:c392:: with SMTP id s18mr10973782wmj.169.1575638726644; Fri, 06 Dec 2019 05:25:26 -0800 (PST) Received: from Martins-MacBook-Pro.local (94.196.152.9.threembb.co.uk. [94.196.152.9]) by smtp.googlemail.com with ESMTPSA id x11sm16942464wre.68.2019.12.06.05.25.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Dec 2019 05:25:25 -0800 (PST) To: pgsql-admin From: Martin Goodson Subject: SSL - automatic entry of certificate passphrase in PostgreSQL 10? Message-ID: <5DEA56C4.7010408@googlemail.com> Date: Fri, 6 Dec 2019 13:25:24 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello. Apologies if this is an easy one, I've been looking around but clearly my google-fu may be weak :) I've recently been asked to enable ssl support on one of our PostgreSQL 10 databases, which I've done. However, the certificate I was given appears to have been generated using a passphrase, and now during server start I'm being prompted (as expected) for that passphrase. I'm concerned that this is going to impact the automatic (re)start of the database after server shutdowns, crashes etc. I understand that there is functionality to support this in PostgreSQL 11 with the ssl_passphrase_command parameter, but I was wondering if there's a way to emulate this in PostgreSQL 10 or any kind of workaround? Or am I stuck with either requesting a new certificate without the passphrase or going to PostgreSQL 11? For information, it's a PostgreSQL 10.5 cluster hosted on a VM running RHEL 7.6. Many thanks! -- Martin Goodson In bed above we're deep asleep, While greater love lies further deep. This dream must end, the world must know, We all depend on the beast below.