From 02c323193728d2bc2d012e0bd5259fa428f0a3ed Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 25 Jul 2003 22:07:44 +0000
Subject: Add mention of new SSL capabilities.
---
doc/src/FAQ/FAQ.html | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 82eed3c326d..641a3de6ea2 100644
--- 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 (pgman@candle.pha.pa.us)
@@ -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.
--
cgit v1.2.3