From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Application name patch - v2 |
Date: | 2009-10-19 08:23:55 |
Message-ID: | 162867790910190123x4ffbe69fwe4b9180b85fb7035@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/10/19 Dave Page <dpage(at)pgadmin(dot)org>:
> On Mon, Oct 19, 2009 at 8:54 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> I dislike write access to app name guc for user too. It's not safe.
>> Maybe only super user can do it?
>
> That'll render it pretty useless, as most applications wouldn't then
> be able to set/reset it when it makes sense to do so.
But application can do it simply via connection string, no? Mostly
applications has connection string in configuration, so I don't see
problem there. And if I would to allow access, then I could to wrap
setting to security definer function.
I see this as security hole. It allows special SQL injection.
Regards
Pavel Stehule
>
>
> --
> Dave Page
> EnterpriseDB UK: http://www.enterprisedb.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-10-19 08:29:51 | Re: Application name patch - v2 |
Previous Message | Heikki Linnakangas | 2009-10-19 08:10:48 | Re: Application name patch - v2 |