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 1qEx0Z-0003G5-CR for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Jun 2023 19:08:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qEx0X-00078m-N8 for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Jun 2023 19:08:45 +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 1qEx0X-00078d-DR for pgsql-hackers@lists.postgresql.org; Thu, 29 Jun 2023 19:08:45 +0000 Received: from relay2-d.mail.gandi.net ([2001:4b98:dc4:8::222]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qEx0U-0019Bj-3h for pgsql-hackers@postgresql.org; Thu, 29 Jun 2023 19:08:43 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id E8F9E40002; Thu, 29 Jun 2023 19:08:36 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------sSkp863gwRkL2yLkJBPozFe2" Message-ID: <94da5be0-a2e8-8e22-d170-012410e7c9a3@dunslane.net> Date: Thu, 29 Jun 2023 15:08:35 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations. Content-Language: en-US To: Robert Haas , Jeff Davis Cc: Tom Lane , Noah Misch , "pgsql-hackers@postgresql.org" References: <89a415b86d5421941e4281ba5bf6288934078624.camel@j-davis.com> <573014.1686375211@sss.pgh.pa.us> <20230612170510.GA201972@gust.leadboat.com> <20230613182920.GA259321@gust.leadboat.com> <1799839.1686687804@sss.pgh.pa.us> <4df537f5a0d8c0ceac3eec3809d1144880b8e76d.camel@j-davis.com> <578fb4be80247570e6a05924908765a0b345971e.camel@j-davis.com> From: Andrew Dunstan In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------sSkp863gwRkL2yLkJBPozFe2 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2023-06-29 Th 11:19, Robert Haas wrote: > > Now we're proposing to ship a brand-new feature with a hole that we > definitely already know exists. I can't understand that at all. Should > we just go file the CVE against ourselves right now, then? Seriously, > what are we doing? > > If we're not going to fix the feature so that it doesn't break the > security model, we should probably just revert it. I don't understand > at all the idea of shipping something that we 100% know is broken. > > +1 cheers andrew -- Andrew Dunstan EDB:https://www.enterprisedb.com --------------sSkp863gwRkL2yLkJBPozFe2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit


On 2023-06-29 Th 11:19, Robert Haas wrote:

Now we're proposing to ship a brand-new feature with a hole that we
definitely already know exists. I can't understand that at all. Should
we just go file the CVE against ourselves right now, then? Seriously,
what are we doing?

If we're not going to fix the feature so that it doesn't break the
security model, we should probably just revert it. I don't understand
at all the idea of shipping something that we 100% know is broken.


+1


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com
--------------sSkp863gwRkL2yLkJBPozFe2--