Laurenz Albe <laurenz.albe@xxxxxxxxxxx> writes: > On Fri, 2024-10-18 at 15:41 +0530, sreekanta reddy wrote: >> When creating or altering a user's password, the log file captures the password in plain text format, which could be a potential security risk. >> However, when using the \password command in psql, the password is logged in its hashed format (SHA-256), which is a more secure practice. >> I recommend extending this hashed logging format to all password creation and modification operations. > You mean to hash it just for logging? > After you sent it to the server in clear text, so that the DBA could capture it with an > event trigger? Where is the point? The log file is to be treated as sensitive data. Yeah. To enlarge on that: if you are capturing SQL commands in the log file, they most likely contain all kinds of sensitive data --- think credit card numbers, bank account numbers, HIPAA-protected medical details, yadda yadda. Most of that, the database has no idea whether it's sensitive, so "please hide sensitive data in the log" is a non-starter. You have to guard the postmaster log about as carefully as you guard the database contents. regards, tom lane
