From: Tom Lane <tgl@sss.pgh.pa.us>
To: Don Seiler <don@seiler.us>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Passwords in clear text in server log
In-reply-to: 
 <CAHJZqBDe1-oiYtdh5pcWLAhr3jsDMFQg4miv3PYADH3YWKqZ2w@mail.gmail.com>
References: 
 <CAHJZqBDe1-oiYtdh5pcWLAhr3jsDMFQg4miv3PYADH3YWKqZ2w@mail.gmail.com>
Comments: In-reply-to Don Seiler <don@seiler.us>
	message dated "Wed, 11 Oct 2017 09:30:50 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9071.1507733313.1@sss.pgh.pa.us>
Date: Wed, 11 Oct 2017 10:48:33 -0400
Message-ID: <9072.1507733313@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Don Seiler <don@seiler.us> writes:
> When I run a CREATE USER or ALTER USER statement and set a password for a
> user, that statement gets printed to the server log, along with the
> password, IN CLEAR TEXT.

This is why psql has provisions for encrypting a new password on the
client side --- see \password.

More generally, almost any SQL command might contain data that somebody
thinks is sensitive for some purpose or other.  If you're going to log
commands, it behooves you to make sure the log is not widely readable.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin