mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Clarify documentation about SSL passphrases

Browse Source 
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.
This commit is contained in:
Peter Eisentraut 2019-11-09 10:13:14 +01:00
parent 27b59d619d
commit d2d4c35080
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/src/sgml/runtime.sgml
View File

@ -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>