Re: Hardening PostgreSQL via (optional) ban on local file system access - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Hardening PostgreSQL via (optional) ban on local file system access
Date
Msg-id CAKFQuwbYaDp2Hv0TA-FJ23Hh+dSYrhdA8BUEPXMwHRmCMC2ZKA@mail.gmail.com
Whole thread Raw
In response to Re: Hardening PostgreSQL via (optional) ban on local file system access  (Gurjeet Singh <gurjeet@singh.im>)
Responses Re: Hardening PostgreSQL via (optional) ban on local file system access  (Hannu Krosing <hannuk@google.com>)
List pgsql-hackers


On Friday, June 24, 2022, Gurjeet Singh <gurjeet@singh.im> wrote:
On Fri, Jun 24, 2022 at 4:13 PM Andres Freund <andres@anarazel.de> wrote:
> On 2022-06-25 00:08:13 +0200, Hannu Krosing wrote:

> > 3) should this be back-patched (we can provide batches for all
> > supported PgSQL versions)
>
> Err, what?

Translation: Backpatching these changes to any stable versions will
not be acceptable (per the project versioning policy [1]), since these
changes would be considered new feature. These changes can break
installations, if released in a minor version.


No longer having the public schema in the search_path was a feature that got back-patched, with known bad consequences, without any way for the DBA to voice their opinion on the matter.  This proposal seems similar enough to at least ask the question, with full DBA control and no known bad consequences.

David J.

pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Hardening PostgreSQL via (optional) ban on local file system access
Next
From: Hannu Krosing
Date:
Subject: Re: Hardening PostgreSQL via (optional) ban on local file system access