| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Steve Atkins" <steve(at)blighty(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remote administration functionality |
| Date: | 2005-07-31 08:49:48 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E485078B@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
-----Original Message-----
From: pgsql-hackers-owner(at)postgresql(dot)org on behalf of Steve Atkins
Sent: Sun 7/31/2005 5:35 AM
To: PostgreSQL-development
Subject: Re: [HACKERS] Remote administration functionality
> So, while I can see the attraction of being able to futz with the
> database security configuration through a PHP web interface running on
> an unpatched Apache build somewhere out on the open internet (and
> would like to be able to do so myself, sometimes) I'd really, really
> like to see the ability to disable as much of this at compile time as
> is convenient.
Yes, Tom expressed a similar concern and suggested he would be happy with a GUC to disable potentially dangerous functions (which we could later extend to other features like untrusted PLs). This GUC was added to the patch by Magnus yesterday and would allow you to secure your system from attacks via the new functions in an insecure environment.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2005-07-31 08:55:19 | Re: Remote administration functionality |
| Previous Message | Tom Lane | 2005-07-31 07:30:47 | Re: [COMMITTERS] pgsql: Add GUC variables to control keep-alive |