pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Robert Haas <robertmhaas@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations.
Date: Thu, 29 Jun 2023 15:08:35 -0400
Message-ID: <94da5be0-a2e8-8e22-d170-012410e7c9a3@dunslane.net> (raw)
In-Reply-To: <CA+TgmoZVCHERUkXhAMT2Er-sKBc5C6_iX+TpxxivBevDHzq2TQ@mail.gmail.com>
References: <E1q7j7Y-000z1H-Hr@gemulon.postgresql.org>
	<89a415b86d5421941e4281ba5bf6288934078624.camel@j-davis.com>
	<d20864b929ff769a0ebf772359719f05bb6982cd.camel@j-davis.com>
	<573014.1686375211@sss.pgh.pa.us>
	<20230612170510.GA201972@gust.leadboat.com>
	<f53df2dbe11bb42764bcdd003a54aa29c9bb6137.camel@j-davis.com>
	<20230613182920.GA259321@gust.leadboat.com>
	<1799839.1686687804@sss.pgh.pa.us>
	<4df537f5a0d8c0ceac3eec3809d1144880b8e76d.camel@j-davis.com>
	<CA+TgmoYtJU0KknWr11W--wK=4eJtdHOgupyT=beZVPC8P=o+YA@mail.gmail.com>
	<578fb4be80247570e6a05924908765a0b345971e.camel@j-davis.com>
	<CA+TgmoZVCHERUkXhAMT2Er-sKBc5C6_iX+TpxxivBevDHzq2TQ@mail.gmail.com>


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

view thread (59+ messages)  latest in thread

Message-ID: <94da5be0-a2e8-8e22-d170-012410e7c9a3@dunslane.net>
Permalink:  ../94da5be0-a2e8-8e22-d170-012410e7c9a3@dunslane.net/
Also on:    postgresql.org/message-id/94da5be0-a2e8-8e22-d170-012410e7c9a3@dunslane.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: andrew@dunslane.net, robertmhaas@gmail.com, pgsql@j-davis.com, tgl@sss.pgh.pa.us, noah@leadboat.com, pgsql-hackers@postgresql.org
  Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations.
  In-Reply-To: <94da5be0-a2e8-8e22-d170-012410e7c9a3@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox