Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YRWOL-00077n-MB for pgsql-hackers@arkaria.postgresql.org; Sat, 28 Feb 2015 01:40:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YRWOK-0005uF-EU for pgsql-hackers@arkaria.postgresql.org; Sat, 28 Feb 2015 01:40:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YRWOJ-0005u9-88 for pgsql-hackers@postgresql.org; Sat, 28 Feb 2015 01:40:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YRWOF-0001G8-VK for pgsql-hackers@postgresql.org; Sat, 28 Feb 2015 01:40:26 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t1S1eIug029711; Fri, 27 Feb 2015 20:40:18 -0500 From: Tom Lane To: Stephen Frost cc: Pavel Stehule , Tomas Vondra , PostgreSQL Hackers Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission In-reply-to: <20150228003749.GU29780@tamriel.snowman.net> References: <54C8156E.1080500@BlueTreble.com> <54C95C4B.2080901@BlueTreble.com> <54F09D68.2090700@2ndquadrant.com> <20150227165950.GP29780@tamriel.snowman.net> <20150227183236.GQ29780@tamriel.snowman.net> <20150227195529.GS29780@tamriel.snowman.net> <12545.1425072391@sss.pgh.pa.us> <20150228003749.GU29780@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Fri, 27 Feb 2015 19:37:49 -0500" Date: Fri, 27 Feb 2015 20:40:18 -0500 Message-ID: <29710.1425087618@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Stephen Frost writes: > I understand that there may be objections to that on the basis that it's > work that's (other than for this case) basically useless, Got it in one. I'm also not terribly happy about leaving security-relevant data sitting around in backend memory 100% of the time. We have had bugs that exposed backend memory contents for reading without also granting the ability to execute arbitrary code, so I think doing this does represent a quantifiable decrease in the security of pg_hba.conf. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers