Re: Securing stored procedures and triggers - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Securing stored procedures and triggers
Date
Msg-id dcc563d10710311110l35e6d463q39c4429f79b5121e@mail.gmail.com
Whole thread Raw
In response to Re: Securing stored procedures and triggers  (Douglas McNaught <doug@mcnaught.org>)
Responses Re: Securing stored procedures and triggers  (Douglas McNaught <doug@mcnaught.org>)
List pgsql-general
On 10/31/07, Douglas McNaught <doug@mcnaught.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.

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Automatic schema updates
Next
From: Ron St-Pierre
Date:
Subject: Re: getting list of tables from command line