rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Peter Eisentraut 2019-11-09 10:13:14 +01:00
parent 7961da1887
commit f77be47d33
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

@ -2246,8 +2246,9 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
If the private key is protected with a passphrase, the If the private key is protected with a passphrase, the
server will prompt for the passphrase and will not start until it has server will prompt for the passphrase and will not start until it has
been entered. been entered.
Using a passphrase also disables the ability to change the server's SSL Using a passphrase by default disables the ability to change the server's
configuration without a server restart. 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 Furthermore, passphrase-protected private keys cannot be used at all
on Windows. on Windows.
</para> </para>