postgres.git / summary / log / commit / refs

commit    0625dbb0b96e2ecd557eb5bcdc458679123951db
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue Dec 15 21:57:23 2015 +0000
First released in: 9.6.0, 9.5.0

    Document use of Subject Alternative Names in SSL server certificates.
    
    Commit acd08d764 did not bother with updating the documentation.


 doc/src/sgml/libpq.sgml | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 9c0e4c8f9c6..2328d8f5f21 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -7296,10 +7296,12 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
   </para>
 
   <para>
-   In <literal>verify-full</> mode, the <literal>cn</> (Common Name) attribute
-   of the certificate is matched against the host name. If the <literal>cn</>
-   attribute starts with an asterisk (<literal>*</>), it will be treated as
-   a wildcard, and will match all characters <emphasis>except</> a dot
+   In <literal>verify-full</> mode, the host name is matched against the
+   certificate's Subject Alternative Name attribute(s), or against the
+   Common Name attribute if no Subject Alternative Name of type dNSName is
+   present.  If the certificate's name attribute starts with an asterisk
+   (<literal>*</>), the asterisk will be treated as
+   a wildcard, which will match all characters <emphasis>except</> a dot
    (<literal>.</>). This means the certificate will not match subdomains.
    If the connection is made using an IP address instead of a host name, the
    IP address will be matched (without doing any DNS lookups).


[parent: bfc7f5dd5dc6]