aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-11-09 10:13:14 +0100
committerPeter Eisentraut <peter@eisentraut.org>2019-11-09 10:15:09 +0100
commitf77be47d339898aeab97ba3fb6c649512e34cab7 (patch)
tree1ce48ef57c0661014cae99a21c88d884850bcea7
parent7961da1887afb04184fd9169dec01870d1003d4a (diff)
downloadpostgresql-f77be47d339898aeab97ba3fb6c649512e34cab7.tar.gz
postgresql-f77be47d339898aeab97ba3fb6c649512e34cab7.zip
doc: Clarify documentation about SSL passphrases
The previous statement that using a passphrase disables the ability to change the server's SSL configuration without a server restart was no longer completely true since the introduction of ssl_passphrase_command_supports_reload.
-rw-r--r--doc/src/sgml/runtime.sgml5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 333adda4086..f16bc455822 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -2246,8 +2246,9 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
If the private key is protected with a passphrase, the
server will prompt for the passphrase and will not start until it has
been entered.
- Using a passphrase also disables the ability to change the server's SSL
- configuration without a server restart.
+ Using a passphrase by default disables the ability to change the server's
+ SSL configuration without a server restart, but see <xref
+ linkend="guc-ssl-passphrase-command-supports-reload"/>.
Furthermore, passphrase-protected private keys cannot be used at all
on Windows.
</para>