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

From Douglas McNaught
Subject Re: Securing stored procedures and triggers
Date
Msg-id 877il3qpv0.fsf@suzuka.mcnaught.org
Whole thread Raw
In response to Securing stored procedures and triggers  (mgould <mgould@allcoast.net>)
Responses Re: Securing stored procedures and triggers
Re: Securing stored procedures and triggers
List pgsql-general
mgould <mgould@allcoast.net> writes:

> We are currently migrating from Sybase's ASA 9/10 to PostGres 8.2.4.
> One of the features that is really nice in ASA is the ability to add
> the attribute hidden to a Create procedure, Create function and
> Create trigger.  Essentially what this does is encrypt the code so
> that if anyone or any utility gets into the database they cannot see
> any of the actual code.  This is a great feature for protecting
> intellectual processing techniques.  I don't know if there is anyway
> to do this in PostGres.  Before the hidden feature was added, we had
> a competitor steal some of our stored procedure processing code.  Is
> there anyway to protect this from happening in PostGres?

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

-Doug

pgsql-general by date:

Previous
From: Reece Hart
Date:
Subject: Re: getting list of tables from command line
Next
From: "T.J. Adami"
Date:
Subject: Re: getting list of tables from command line