Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1krPy7-0008Mt-9Z for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Dec 2020 18:31:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1krPy5-0005bf-PP for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Dec 2020 18:31:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1krPy5-0005bY-IV for pgsql-hackers@lists.postgresql.org; Mon, 21 Dec 2020 18:31:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1krPy3-0006kM-EB for pgsql-hackers@postgresql.org; Mon, 21 Dec 2020 18:31:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0BLIVWaY543837; Mon, 21 Dec 2020 13:31:32 -0500 From: Tom Lane To: Jeff Janes cc: Stephen Frost , Magnus Hagander , Thomas Munro , k.yudhveer@gmail.com, pgsql-hackers Subject: Re: BUG #16079: Question Regarding the BUG #16064 In-reply-to: References: <16079-29e9c038e1463751@postgresql.org> <20191028154754.GS6962@tamriel.snowman.net> <20201221005825.GQ16415@tamriel.snowman.net> Comments: In-reply-to Jeff Janes message dated "Mon, 21 Dec 2020 12:26:17 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <543835.1608575492.1@sss.pgh.pa.us> Date: Mon, 21 Dec 2020 13:31:32 -0500 Message-ID: <543836.1608575492@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jeff Janes writes: > On Sun, Dec 20, 2020 at 7:58 PM Stephen Frost wrote: >> * Magnus Hagander (magnus@hagander.net) wrote: >>> Maybe we should do the same for LDAP (and RADIUS)? This seems like a >>> better place to put it than to log it at every time it's received? >> A dollar short and a year late, but ... +1. > I would suggest going further. I would make the change on the client side, > and have libpq refuse to send unhashed passwords without having an > environment variable set which allows it. As noted, that would break LDAP and RADIUS auth methods; likely also PAM. > What is the value of logging on the server side? I do agree with this point, but mostly on the grounds of "nobody reads the server log". regards, tom lane