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

From Albe Laurenz
Subject Re: Securing stored procedures and triggers
Date
Msg-id D960CB61B694CF459DCFB4B0128514C27F71F7@exadv11.host.magwien.gv.at
Whole thread Raw
In response to Securing stored procedures and triggers  (mgould <mgould@allcoast.net>)
List pgsql-general
mgould wrote:
> 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?

Not with PL/pgSQL.

That's probably not what you want, but you can write
stored procedures in C and ship the shared library.

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: configure password
Next
From: "Scott Marlowe"
Date:
Subject: Re: Join between tables of two or more databases