| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: search path security issue? |
| Date: | 2017-10-08 18:34:36 |
| Message-ID: | f3ee3b67-82ee-9a67-23be-c6ba199a80fd@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/06/2017 12:52 AM, Magnus Hagander wrote:
> It would be a nice feature to have in general, like a "basic guc
> permissions" thing. At least allowing a superuser to prevent exactly
> this. You could argue the same thing for example for memory parameters
> and such. We have no permissions at all when it comes to userset gucs
> today -- and of course, if something should be added about this, it
> should be done in a way that works for all the userset variables, not
> just search_path.
+1
I have wished for exactly that more than once before.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-10-08 21:11:44 | Re: Discussion on missing optimizations |
| Previous Message | Peter Geoghegan | 2017-10-08 17:29:06 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |