| From: | daveg <daveg(at)sonic(dot)net> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: dblink connection security |
| Date: | 2007-07-09 21:04:03 |
| Message-ID: | 20070709210403.GA30237@sonic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Mon, Jul 09, 2007 at 06:13:54PM +0100, Gregory Stark wrote:
> I'm not suggesting making dblink super-user only. Only revoking public execute
> bits in the default install script. That doesn't affect users upgrading so I
> don't see a backwards-compatibility issue.
>
> The doc changes are going to say to be very careful who you grant access to
> dblink to which means not granting public execute access if you have multiple
> users. All I'm suggesting is that the default install script should just do
> that rather than do something that the docs will then recommend you undo.
+1
-dg
--
David Gould daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with simpletons.
- Doug Earp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-09 23:29:32 | Re: Maintaining cluster order on insert |
| Previous Message | Stephen Frost | 2007-07-09 18:33:52 | Re: dblink connection security |