Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit02c3231

Browse files
committed
Add mention of new SSL capabilities.
1 parentad73f6b commit02c3231

File tree

2 files changed

+17
-8
lines changed

2 files changed

+17
-8
lines changed

‎doc/FAQ

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated:Wed Jul23 12:53:27 EDT 2003
4+
Last updated:Fri Jul25 18:07:30 EDT 2003
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -1111,8 +1111,12 @@ CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
11111111

11121112
* contrib/pgcrypto contains many encryption functions for use in SQL
11131113
queries.
1114-
* The only way to encrypt transmission from the client to the server
1115-
is by using hostssl in pg_hba.conf.
1114+
* To encrypt transmission from the client to the server, the server
1115+
must have the ssl option set to true in postgresql.conf, and an
1116+
applicable host or hostssl record must exist in pg_hba.conf, and
1117+
the client sslmode must not be disable. (Note that it is also
1118+
possible to use a third-party encrypted transport, such as stunnel
1119+
or ssh, rather than PostgreSQL's native SSL connections.)
11161120
* Database user passwords are automatically encrypted when stored in
11171121
version 7.3. In previous versions, you must enable the option
11181122
PASSWORD_ENCRYPTION in postgresql.conf.

‎doc/src/FAQ/FAQ.html

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
alink="#0000ff">
1111
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1212

13-
<P>Last updated:Wed Jul23 12:53:27 EDT 2003</P>
13+
<P>Last updated:Fri Jul25 18:07:30 EDT 2003</P>
1414

1515
<P>Current maintainer: Bruce Momjian (<Ahref=
1616
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@@ -1401,10 +1401,15 @@ <H4><A name="4.28">4.28</A>) What encryption options are available?
14011401
<UL>
14021402
<LI><I>contrib/pgcrypto</I> contains many encryption functions for
14031403
use in<SMALL>SQL</SMALL> queries.</LI>
1404-
<LI>The only way to encrypt transmission from the client to the
1405-
server is by using<I>hostssl</I> in<I>pg_hba.conf</I>.</LI>
1406-
<LI>Database user passwords are automatically encrypted when stored
1407-
in version 7.3. In previous versions, you must enable the option
1404+
<LI>To encrypt transmission from the client to the server, the server
1405+
must have the<I>ssl</I> option set to<I>true</I> in<I>postgresql.conf,
1406+
</I> and an applicable<I>host</I> or<I>hostssl</I> record must exist in
1407+
<I>pg_hba.conf</I>, and the client<I>sslmode</I> must not be
1408+
<I>disable.</I> (Note that it is also possible to use a third-party
1409+
encrypted transport, such as stunnel or ssh, rather than PostgreSQL's
1410+
native SSL connections.)
1411+
<LI>Database user passwords are automatically encrypted when stored in
1412+
version 7.3. In previous versions, you must enable the option
14081413
<I>PASSWORD_ENCRYPTION</I> in<I>postgresql.conf</I>.</LI>
14091414
<LI>The server can run using an encrypted file system.</LI>
14101415
</UL>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp