Re: Securing stored procedures and triggers

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Douglas McNaught" <doug(at)mcnaught(dot)org>
Cc: fasupport(at)allcoast(dot)net, pgsql-general(at)postgresql(dot)org
Subject: Re: Securing stored procedures and triggers
Date: 2007-10-31 18:10:05
Message-ID: dcc563d10710311110l35e6d463q39c4429f79b5121e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/31/07, Douglas McNaught <doug(at)mcnaught(dot)org> wrote:

> The only bulletproof way to do this currently is to write all your
> stored functions in C and load them as a shared library.

Well, as I pointed out in my post, even that's not bullet-proof. As
long as decompilers / debuggers etc... exist, then compiling is just a
small barrier to a good hacker. The only way to win is not to play,
i.e. keep the code in house.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Reg Me Please 2007-10-31 18:26:51 Re: Securing stored procedures and triggers
Previous Message Scott Marlowe 2007-10-31 18:08:30 Re: Automatic schema updates