From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Marc Cousin <cousinmarc(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8 |
Date: | 2018-07-13 22:16:32 |
Message-ID: | 59f8f5e3-2b2d-36c4-c5bd-9e3606cd008b@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 07/13/2018 05:23 PM, Tom Lane wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> I think serious consideration needs to be given to ways to allow the user
>> of pg_dump/pg_restore to choose the prior, less secure, mode of operation​.
>> IMO the risk surface presented to support back-patching the behavioral
>> changes was not severe enough to do so in the first place. I'm presuming
>> undoing the back-patch will be shot down without mercy but at least
>> consider an escape hatch for unafflicted secure systems that just happen to
>> depend on search_path more than a super-hardened system would.
> FWIW, in the security team's discussions of CVE-2018-1058, I argued
> strenuously in favor of providing a way to run pg_dump/pg_restore with
> the system's default search_path as before. I lost the argument;
> but maybe the need for features like this shows that we are not really
> ready to insist on unconditional security there.
>
>
I don't remember that, TBH.
Certainly this problem seems nasty enough that we should possibly
revisit the issue.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-07-13 22:50:33 | Re: function lca('{}'::ltree[]) caused DB Instance crash |
Previous Message | Tom Lane | 2018-07-13 21:23:40 | Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-07-13 22:50:33 | Re: function lca('{}'::ltree[]) caused DB Instance crash |
Previous Message | Daniel Gustafsson | 2018-07-13 22:14:51 | Re: Finding database for pg_upgrade missing library |