Add mention of new SSL capabilities.

diff --git a/doc/FAQ b/doc/FAQ
index 2c082ac63d07f349c7115b03ce35d74c1f434f16..66d3c9bbb8a74c1fd962f5bc63ae9a3ead817ae1 100644 (file)
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
 
                 Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Wed Jul 23 12:53:27 EDT 2003
+   Last updated: Fri Jul 25 18:07:30 EDT 2003
    
    Current maintainer: Bruce Momjian ([email protected])
    
@@ -1111,8 +1111,12 @@ CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
     
      * contrib/pgcrypto contains many encryption functions for use in SQL
        queries.
-     * The only way to encrypt transmission from the client to the server
-       is by using hostssl in pg_hba.conf.
+     * To encrypt transmission from the client to the server, the server
+       must have the ssl option set to true in postgresql.conf, and an
+       applicable host or hostssl record must exist in pg_hba.conf, and
+       the client sslmode must not be disable. (Note that it is also
+       possible to use a third-party encrypted transport, such as stunnel
+       or ssh, rather than PostgreSQL's native SSL connections.)
      * Database user passwords are automatically encrypted when stored in
        version 7.3. In previous versions, you must enable the option
        PASSWORD_ENCRYPTION in postgresql.conf.

diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 82eed3c326d82eb00cab1f8baf19c4240366dd7b..641a3de6ea2c9b82cc74eedb2007c6494433d448 100644 (file)
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
   alink="#0000ff">
     Frequently Asked Questions (FAQ) for PostgreSQL
 
-    Last updated: Wed Jul 23 12:53:27 EDT 2003
+    Last updated: Fri Jul 25 18:07:30 EDT 2003
 
     Current maintainer: Bruce Momjian (
     "mailto:[email protected]">[email protected])
@@ -1401,10 +1401,15 @@ BYTEA           bytea           variable-length byte array (null-byte safe)
     
     contrib/pgcrypto contains many encryption functions for
     use in SQL queries.
-    The only way to encrypt transmission from the client to the
-    server is by using hostssl in pg_hba.conf.
-    Database user passwords are automatically encrypted when stored
-    in version 7.3. In previous versions, you must enable the option
+    To encrypt transmission from the client to the server, the server
+    must have the ssl option set to true in postgresql.conf,
+     and an applicable host or hostssl record must exist in
+    pg_hba.conf, and the client sslmode must not be
+    disable. (Note that it is also possible to use a third-party
+    encrypted transport, such as stunnel or ssh, rather than PostgreSQL's
+    native SSL connections.)
+    Database user passwords are automatically encrypted when stored in
+    version 7.3. In previous versions, you must enable the option
     PASSWORD_ENCRYPTION in postgresql.conf.
     The server can run using an encrypted file system.