Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2MwW-0007Ul-V8 for pgsql-admin@arkaria.postgresql.org; Wed, 11 Oct 2017 19:45:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e2MwW-0001P0-Bi for pgsql-admin@arkaria.postgresql.org; Wed, 11 Oct 2017 19:45:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e2Muh-0006Xu-Dl for pgsql-admin@postgresql.org; Wed, 11 Oct 2017 19:43:31 +0000 Received: from smtprelay0204.b.hostedemail.com ([64.98.42.204] helo=smtprelay.b.hostedemail.com) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e2Mue-00066W-9l for pgsql-admin@postgresql.org; Wed, 11 Oct 2017 19:43:30 +0000 Received: from filter.hostedemail.com (10.5.19.248.rfc1918.com [10.5.19.248]) by smtprelay03.b.hostedemail.com (Postfix) with ESMTP id 2456A1A701E; Wed, 11 Oct 2017 19:43:26 +0000 (UTC) X-Session-Marker: 616C76686572726540616C76682E6E6F2D69702E6F7267 X-Spam-Summary: 50,0,0,,d41d8cd98f00b204,alvherre@alvh.no-ip.org,:::::,RULES_HIT:41:355:379:599:967:973:988:989:1256:1260:1277:1311:1312:1313:1314:1345:1359:1437:1515:1516:1518:1519:1534:1538:1593:1594:1595:1596:1711:1714:1730:1747:1777:1792:2393:2525:2560:2563:2682:2685:2693:2828:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3351:3865:3866:3867:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4416:4605:5007:6119:6261:7903:9025:9121:10004:10400:10450:10455:10848:11232:11658:11914:13069:13161:13229:13311:13357:13439:13894:13895:14764:19904:19999:21080:21627:30051:30054,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:2,LUA_SUMMARY:none X-HE-Tag: shoe23_c0668d47317 X-Filterd-Recvd-Size: 1504 Received: from alvin.alvh.no-ip.org (unknown [92.59.181.161]) (Authenticated sender: alvherre@alvh.no-ip.org) by omf14.b.hostedemail.com (Postfix) with ESMTPA; Wed, 11 Oct 2017 19:43:25 +0000 (UTC) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 76069877; Wed, 11 Oct 2017 21:43:23 +0200 (CEST) Date: Wed, 11 Oct 2017 21:43:23 +0200 From: Alvaro Herrera To: Don Seiler Cc: Tom Lane , pgsql-admin Subject: Re: Passwords in clear text in server log Message-ID: <20171011194323.s2alxtl3krdvj7hj@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Don Seiler wrote: > If you're going to log statements that fail to parse, then yes it will make > it harder to close these loopholes. That's also new to me, coming from a > different RDBMS world. It logs neither bad (failed to parse) SQL nor user > passwords. Actually, I do wonder why we log statements that fail to parse. Surely the client ought to know that it failed, but what is the value of additionally storing the query in the server log? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin