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

Commitc0252d7

Browse files
committed
doc: warn about security issues around log files
Reported-by: Simon RiggsDiscussion:https://postgr.es/m/CANP8+jJESuuXYq9Djvf-+tx2vY2OFLmfEuu+UvwHNJ1RT7iJCQ@mail.gmail.comAuthor: Simon RiggsBackpatch-through: 10
1 parent72d76a4 commitc0252d7

File tree

2 files changed

+30
-1
lines changed

2 files changed

+30
-1
lines changed

‎doc/src/sgml/config.sgml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6242,6 +6242,13 @@ local0.* /var/log/postgresql
62426242
<sect2 id="runtime-config-logging-what">
62436243
<title>What to Log</title>
62446244

6245+
<note>
6246+
<para>
6247+
What you choose to log can have security implications; see
6248+
<xref linkend="logfile-maintenance"/>.
6249+
</para>
6250+
</note>
6251+
62456252
<variablelist>
62466253

62476254
<varlistentry id="guc-application-name" xreflabel="application_name">
@@ -6684,6 +6691,10 @@ log_line_prefix = '%m [%p] %q%u@%d/%a '
66846691
planning). Set <varname>log_min_error_statement</varname> to
66856692
<literal>ERROR</literal> (or lower) to log such statements.
66866693
</para>
6694+
<para>
6695+
Logged statements might reveal sensitive data and even contain
6696+
plaintext passwords.
6697+
</para>
66876698
</note>
66886699
</listitem>
66896700
</varlistentry>

‎doc/src/sgml/maintenance.sgml

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -939,7 +939,25 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
939939
It is a good idea to save the database server's log output
940940
somewhere, rather than just discarding it via <filename>/dev/null</filename>.
941941
The log output is invaluable when diagnosing
942-
problems. However, the log output tends to be voluminous
942+
problems.
943+
</para>
944+
945+
<note>
946+
<para>
947+
The server log can contain sensitive information and needs to be protected,
948+
no matter how or where it is stored, or the destination to which it is routed.
949+
For example, some DDL statements might contain plaintext passwords or other
950+
authentication details. Logged statements at the <literal>ERROR</literal>
951+
level might show the SQL source code for applications
952+
and might also contain some parts of data rows. Recording data, events and
953+
related information is the intended function of this facility, so this is
954+
not a leakage or a bug. Please ensure the server logs are visible only to
955+
appropriately authorized people.
956+
</para>
957+
</note>
958+
959+
<para>
960+
Log output tends to be voluminous
943961
(especially at higher debug levels) so you won't want to save it
944962
indefinitely. You need to <emphasis>rotate</emphasis> the log files so that
945963
new log files are started and old ones removed after a reasonable

0 commit comments

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