mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
Add mention of new SSL capabilities.
This commit is contained in:
10
doc/FAQ
10
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 (pgman@candle.pha.pa.us)
|
||||
|
||||
@ -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.
|
||||
|
Reference in New Issue
Block a user