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

Commit5285c5e

Browse files
committed
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.comBackpatch-through: 9.6
1 parent9595383 commit5285c5e

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

‎doc/src/sgml/runtime.sgml

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1922,7 +1922,7 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
19221922
</para>
19231923

19241924
<para>
1925-
The simplestway to prevent spoofingfor <literal>local</>
1925+
Onway to prevent spoofingof <literal>local</>
19261926
connections is to use a Unix domain socket directory (<xref
19271927
linkend="guc-unix-socket-directories">) that has write permission only
19281928
for a trusted local user. This prevents a malicious user from creating
@@ -1934,6 +1934,13 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
19341934
<filename>/tmp</> cleanup script to prevent removal of the symbolic link.
19351935
</para>
19361936

1937+
<para>
1938+
Another option for <literal>local</> connections is for clients to use
1939+
<link linkend="libpq-connect-requirepeer"><literal>requirepeer</></>
1940+
to specify the required owner of the server process connected to
1941+
the socket.
1942+
</para>
1943+
19371944
<para>
19381945
To prevent spoofing on TCP connections, the best solution is to use
19391946
SSL certificates and make sure that clients check the server's certificate.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp