Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs - Mailing list pgsql-bugs

From Daniel Westermann (DWE)
Subject Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
Date
Msg-id GV0P278MB041978A9E389AEE82AF9B6B4D2C52@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
_______________________________________
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Wednesday, February 19, 2025 07:30
To: Matthias Apitz <guru@unixarea.de>
Cc: Indrajeeth Deshmukh <bkindrajeeth@gmail.com>; David Rowley <dgrowleyml@gmail.com>; pgsql-bugs@lists.postgresql.org
<pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
 
Matthias Apitz <guru@unixarea.de> writes:
> What do I have to configure in the PostgreSQL server to get this
> reproduced? I tried:

export PGDATA=/var/tmp/xx; rm -rf $PGDATA; export PGPORT=8888; initdb; echo "logging_collector=on" >>
$PGDATA/postgresql.auto.conf;echo "log_statement=ddl" >> $PGDATA/postgresql.auto.conf; pg_ctl start; psql <<< "create
useru with password 'u'"; cat $PGDATA/log/*; pg_ctl stop 

Regards
Daniel


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
Next
From: Manika Singhal
Date:
Subject: Re: BUG #18819: Error installing Postgresql