Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Matthias Apitz <guru(at)unixarea(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Indrajeeth Deshmukh <bkindrajeeth(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
Date: 2025-02-19 17:48:47
Message-ID: CAKAnmmLoALp_BFsuE_R4OUOfiQrAosG6Mmb=2rz7qgJeqn9y9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>
> testdb=# CREATE USER bla WITH PASSWORD 'bla';
> CREATE ROLE
>

Run these as well to help you debug:

SELECT pg_current_logfile();

SHOW log_statement;

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Vik Fearing 2025-02-19 19:02:34 Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
Previous Message David G. Johnston 2025-02-19 13:46:14 Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE