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:13:14 +0100
commitd2d4c35080026ba3da49583e30c1fd53c9fb22dd (patch)
tree3c03db7fd02ce950bde0cfa4dc2d160be5b3af8e
parent27b59d619ddfb512e3f158a87f557a46f2d5794f (diff)
downloadpostgresql-d2d4c35080026ba3da49583e30c1fd53c9fb22dd.tar.gz
postgresql-d2d4c35080026ba3da49583e30c1fd53c9fb22dd.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 112ae591dc3..a34d31d297a 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -2310,8 +2310,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>