From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, 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 21:23:40 |
Message-ID: | 13033.1531517020@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
"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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2018-07-13 22:16:32 | Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8 |
Previous Message | David G. Johnston | 2018-07-13 21:17:30 | Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8 |
From | Date | Subject | |
---|---|---|---|
Next Message | Nikita Glukhov | 2018-07-13 21:31:50 | Re: [HACKERS] [PATCH] kNN for SP-GiST |
Previous Message | David G. Johnston | 2018-07-13 21:19:29 | Re: pgsql: Fix parallel index and index-only scans to fall back to serial. |