Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
02c32319
Commit
02c32319
authored
Jul 25, 2003
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add mention of new SSL capabilities.
parent
ad73f6b8
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
17 additions
and
8 deletions
+17
-8
doc/FAQ
doc/FAQ
+7
-3
doc/src/FAQ/FAQ.html
doc/src/FAQ/FAQ.html
+10
-5
No files found.
doc/FAQ
View file @
02c32319
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.
...
...
doc/src/FAQ/FAQ.html
View file @
02c32319
...
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated:
Wed Jul 23 12:53:27
EDT 2003
</P>
<P>
Last updated:
Fri Jul 25 18:07:30
EDT 2003
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
<BR>
...
...
@@ -1401,10 +1401,15 @@ BYTEA bytea variable-length byte array (null-byte safe)
<UL>
<LI><I>
contrib/pgcrypto
</I>
contains many encryption functions for
use in
<SMALL>
SQL
</SMALL>
queries.
</LI>
<LI>
The only way to encrypt transmission from the client to the
server is by using
<I>
hostssl
</I>
in
<I>
pg_hba.conf
</I>
.
</LI>
<LI>
Database user passwords are automatically encrypted when stored
in version 7.3. In previous versions, you must enable the option
<LI>
To encrypt transmission from the client to the server, the server
must have the
<I>
ssl
</I>
option set to
<I>
true
</I>
in
<I>
postgresql.conf,
</I>
and an applicable
<I>
host
</I>
or
<I>
hostssl
</I>
record must exist in
<I>
pg_hba.conf
</I>
, and the client
<I>
sslmode
</I>
must not be
<I>
disable.
</I>
(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.)
<LI>
Database user passwords are automatically encrypted when stored in
version 7.3. In previous versions, you must enable the option
<I>
PASSWORD_ENCRYPTION
</I>
in
<I>
postgresql.conf
</I>
.
</LI>
<LI>
The server can run using an encrypted file system.
</LI>
</UL>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment