Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit b0729b8

Browse files
committed
Documentation for wildcard certificates patch
1 parent b64d966 commit b0729b8

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

doc/src/sgml/libpq.sgml

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.271 2008/11/25 19:30:42 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.272 2008/12/02 12:42:11 mha Exp $ -->
22

33
<chapter id="libpq">
44
<title><application>libpq</application> - C Library</title>
@@ -283,6 +283,15 @@
283283
only if the certificate also has just the IP address in the
284284
<literal>cn</> field.
285285
</para>
286+
287+
<para>
288+
If the <literal>cn</> attribute in the certificate sent by the
289+
server starts with an asterisk (<literal>*</>), it will be treated
290+
as a wildcard. This wildcard can only be present at the start of
291+
the value, and will match all characters <emphasis>except</> a
292+
dot (<literal>.</>). This means the certificate will not match
293+
subdomains.
294+
</para>
286295
</listitem>
287296
</varlistentry>
288297

0 commit comments

Comments
 (0)