From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthias Apitz <guru@unixarea.de>
cc: Indrajeeth Deshmukh <bkindrajeeth@gmail.com>,
        David Rowley <dgrowleyml@gmail.com>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in
 Logs
In-reply-to: <Z7Vy4FefAH/Vk+Lc@pureos>
References: <18817-771682052a364bfe@postgresql.org>
 <CAApHDvoCnaLeVO4zdCaYJFBfcuGXYz1W5L917p526nWEcs=gqg@mail.gmail.com>
 <CAAapt1i2Mf=S0FtPz8Z9RNkez=nP50AcYDVC7Dm8r=cskMn7tg@mail.gmail.com>
 <1241094.1739893072@sss.pgh.pa.us> <Z7Vy4FefAH/Vk+Lc@pureos>
Comments: In-reply-to Matthias Apitz <guru@unixarea.de>
	message dated "Wed, 19 Feb 2025 06:57:52 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1951015.1739946618.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Feb 2025 01:30:18 -0500
Message-ID: <1951016.1739946618@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1951016.1739946618%40sss.pgh.pa.us>
Precedence: bulk

Matthias Apitz <guru@unixarea.de> writes:
> What do I have to configure in the PostgreSQL server to get this
> reproduced? I tried:

[ scratches head... ]  Seems like you must be looking in the wrong
log file.  It works for me:

$ psql postgres
psql (18devel)
Type "help" for help.

postgres=3D# set log_statement =3D 'all';
SET
postgres=3D# CREATE USER bla WITH PASSWORD 'bla';
CREATE ROLE
postgres=3D# \q
$ tail .../postmaster.log
...
2025-02-19 01:19:18.638 EST [1949443] LOG:  statement: CREATE USER bla WIT=
H PASSWORD 'bla';

If you're not running with log_statement =3D all, the most likely
scenario is a syntax error:

$ psql postgres
psql (18devel)
Type "help" for help.

postgres=3D# CREATE USER bla WITH PASWORD 'bla';
ERROR:  unrecognized role option "pasword"
LINE 1: CREATE USER bla WITH PASWORD 'bla';
                             ^
postgres=3D# \q
$ tail .../postmaster.log
...
2025-02-19 01:25:39.227 EST [1950440] ERROR:  unrecognized role option "pa=
sword" at character 22
2025-02-19 01:25:39.227 EST [1950440] STATEMENT:  CREATE USER bla WITH PAS=
WORD 'bla';

Of course, this command didn't do anything; but a person reading the
log would have a pretty strong clue what password you were about to
assign.  (And contrarily, Postgres itself would have no clue that
'bla' might be something that needs hiding.)

			regards, tom lane