diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 4e0f5cee23c..1a4118174e8 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,4 +1,4 @@ - + <application>libpq</application> - C Library @@ -4501,7 +4501,7 @@ ldap://ldap.mycompany.com/dc=mycompany,dc=com?uniqueMember?one?(cn=mydatabase) %APPDATA%\postgresql\root.crt.) The SSL connection will fail if the server does not present a certificate; therefore, to - use this feature the server must also have a root.crt file. + use this feature the server must have a server.crt file. Certificate Revocation List (CRL) entries are also checked if the file ~/.postgresql/root.crl exists (%APPDATA%\postgresql\root.crl on Microsoft Windows). diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 61cc6c37b87..9a724098a7c 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,4 +1,4 @@ - + Operating System Environment @@ -1574,10 +1574,11 @@ chmod og-rwx server.key certificates of the CA(s) you wish to check for in the file root.crt in the data directory. When present, a client certificate will be requested from the client - during SSL connection startup, and it must have been signed by one of the - certificates present in root.crt. Certificate - Revocation List (CRL) entries are also checked if the file - root.crl exists. + during SSL connection startup, and it must have been signed by one of + the certificates present in root.crt. (See for a description of how to set up client + certificates.) Certificate Revocation List (CRL) entries are also + checked if the file root.crl exists.