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

From Douglas McNaught
Subject Re: Securing stored procedures and triggers
Date
Msg-id 873avrqd1p.fsf@suzuka.mcnaught.org
Whole thread Raw
In response to Re: Securing stored procedures and triggers  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-general
"Scott Marlowe" <scott.marlowe@gmail.com> writes:

> 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.

Very true, I should have said "semi-bulletproof".  :)

In addition, the "interesting" parts of a C function would be the SPI
queries, which unless further obfuscated would be easily extractable
from the library using strings(1).

-Doug

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Replacing RDBMS
Next
From: Tom Lane
Date:
Subject: Re: Server's Locale