summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2016-08-18 21:41:10 -0400
committerBruce Momjian <bruce@momjian.us>2016-08-18 21:42:04 -0400
commit2b4ae9c29d42ce7b1b7bb947c585b78a21535aa2 (patch)
tree55ab5da22c32533ae339e4e98abee703013999bd
parent0d5afd3f21e1f3bfb76a50aa613620b9caba4a4e (diff)
doc: requirepeer is a way to avoid spoofing
We already mentioned unix_socket_directories as an option. Reported-by: https://www.postgresql.org/message-id/45016837-6cf3-3136-f959-763d06a28076%402ndquadrant.com Backpatch-through: 9.6
-rw-r--r--doc/src/sgml/runtime.sgml9
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 9007987dab5..51d4f9ca1bc 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1913,7 +1913,7 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
</para>
<para>
- The simplest way to prevent spoofing for <literal>local</>
+ On way to prevent spoofing of <literal>local</>
connections is to use a Unix domain socket directory (<xref
linkend="guc-unix-socket-directories">) that has write permission only
for a trusted local user. This prevents a malicious user from creating
@@ -1926,6 +1926,13 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
</para>
<para>
+ Another option for <literal>local</> connections is for clients to use
+ <link linkend="libpq-connect-requirepeer"><literal>requirepeer</></>
+ to specify the required owner of the server process connected to
+ the socket.
+ </para>
+
+ <para>
To prevent spoofing on TCP connections, the best solution is to use
SSL certificates and make sure that clients check the server's certificate.
To do that, the server