From b0729b8d4e521490cb08f182430f4fc7e08209a8 Mon Sep 17 00:00:00 2001
From: Magnus Hagander <magnus@hagander.net>
Date: Tue, 2 Dec 2008 12:42:11 +0000
Subject: [PATCH] Documentation for wildcard certificates patch
---
doc/src/sgml/libpq.sgml | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index e1a1d5a1c58..a9d0d98d04d 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.271 2008/11/25 19:30:42 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.272 2008/12/02 12:42:11 mha Exp $ -->
<chapter id="libpq">
<title><application>libpq</application> - C Library</title>
@@ -283,6 +283,15 @@
only if the certificate also has just the IP address in the
<literal>cn</> field.
</para>
+
+ <para>
+ If the <literal>cn</> attribute in the certificate sent by the
+ server starts with an asterisk (<literal>*</>), it will be treated
+ as a wildcard. This wildcard can only be present at the start of
+ the value, and will match all characters <emphasis>except</> a
+ dot (<literal>.</>). This means the certificate will not match
+ subdomains.
+ </para>
</listitem>
</varlistentry>
--
GitLab