aboutsummaryrefslogtreecommitdiff
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:41:56 -0400
commit5285c5e873d8b622da7007c1628e5afa80f372fb (patch)
tree41b9f2d065c17a82f5dbfd890d8d6bef7aea8d4c
parent9595383bc6fc24d25970374e2eddd5ce6f977f9e (diff)
downloadpostgresql-5285c5e873d8b622da7007c1628e5afa80f372fb.tar.gz
postgresql-5285c5e873d8b622da7007c1628e5afa80f372fb.zip
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 60a06590fec..98752c2875c 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1922,7 +1922,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
@@ -1935,6 +1935,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