From: Joe Conway <mail@joeconway.com>
To: pgsql-docs <pgsql-docs@postgreSQL.org>
To: Peter Eisentraut <peter_e@gmx.net>
Subject: Re: Passphrase protected SSL key and reloads
Date: Wed, 24 Apr 2019 07:22:03 -0400
Message-ID: <cdecbf67-54c6-2522-2d77-abffc3209d23@joeconway.com> (raw)
In-Reply-To: <75731d49-ad04-49b0-7bf7-09c0d89c9473@joeconway.com>
References: <75731d49-ad04-49b0-7bf7-09c0d89c9473@joeconway.com>
(moved from Hackers to docs)
On 1/5/19 4:26 PM, Joe Conway wrote:
> On https://www.postgresql.org/docs/11/ssl-tcp.html it says:
>
> "Using a passphrase also disables the ability to change the server's
> SSL configuration without a server restart."
>
> But as of pg11 we have ssl_passphrase_command_supports_reload, which as
> I understand it should allow this if the passphrase command is not
> interactive. Per
> https://www.postgresql.org/docs/11/runtime-config-connection.html#GUC-SSL-PASSPHRASE-COMMAND-SUPPORT...
>
> "Setting this parameter to true might be appropriate if the passphrase
> is obtained from a file, for example."
>
> Am I misunderstanding, or was the former quote missed when updating the
> docs for pg11?
Since I am already thinking about pgsql-docs today -- any comment on this?
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
Attachments:
signature.asc (application/pgp-signature, 832B) download
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-docs@postgresql.org
Cc: mail@joeconway.com, peter_e@gmx.net
Subject: Re: Passphrase protected SSL key and reloads
In-Reply-To: <cdecbf67-54c6-2522-2d77-abffc3209d23@joeconway.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