-<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.252 2007/12/28 16:21:08 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.253 2008/01/08 18:07:38 momjian Exp $ -->
<chapter id="libpq">
<title><application>libpq</application> - C Library</title>
to inside <application>libpq</application>), you can use
<function>PQinitSSL(int)</> to tell <application>libpq</application>
that the <acronym>SSL</> library has already been initialized by your
- application.
+ application. See <ulink
+ url="http://h71000.www7.hp.com/doc/83final/BA554_90007/ch04.html"></ulink>
+ for details on the SSL API.
</para>
<table id="libpq-ssl-file-usage">
-<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.401 2007/12/29 04:59:27 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.402 2008/01/08 18:07:38 momjian Exp $ -->
<chapter Id="runtime">
<title>Operating System Environment</title>
verify that the client's certificate is signed by one of the trusted
certificate authorities. Certificate Revocation List (CRL) entries
are also checked if the file <filename>root.crl</filename> exists.
+ (See <ulink
+ url="http://h71000.www7.hp.com/DOC/83final/BA554_90007/ch04s02.html"></>
+ for diagrams showing SSL certificate usage.)
</para>
<para>