Re: dump/restore problem due to CVE-2018-1058 (9.5.12) - Mailing list pgsql-general

From Adrian Klaver
Subject Re: dump/restore problem due to CVE-2018-1058 (9.5.12)
Date
Msg-id 359c4b87-9c36-b251-f65c-fc9bcf2d4412@aklaver.com
Whole thread Raw
In response to Re: dump/restore problem due to CVE-2018-1058 (9.5.12)  (Rory Campbell-Lange <rory@campbell-lange.net>)
List pgsql-general
On 04/08/2018 11:01 AM, Rory Campbell-Lange wrote:
> Thanks for your comprehensive response, Adrian.

> 
> Fair enough. It is however a tedious problem to resolve in a large
> code base and it would be cool to have a new "--set-search-path"
> option to pg_dump to override it.

 From other posts that covered similar ground I would say other people 
would agree. I am guessing the response you will get from those that can 
make the changes is that would be just delaying the inevitable. You can 
always ask though:)

> 
> Thanks again
> Rory
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Rory Campbell-Lange
Date:
Subject: Re: dump/restore problem due to CVE-2018-1058 (9.5.12)
Next
From: Guyren Howe
Date:
Subject: Rationale for aversion to the central database?