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

From Reg Me Please
Subject Re: Securing stored procedures and triggers
Date
Msg-id 200710311926.51473.regmeplease@gmail.com
Whole thread Raw
In response to Re: Securing stored procedures and triggers  (Douglas McNaught <doug@mcnaught.org>)
List pgsql-general
There's not bulletproof way, in my opinion.

If they copy the whole DB structure *and* the object binaries they'll
have the very same functionalities!

Il Wednesday 31 October 2007 16:13:23 Douglas McNaught ha scritto:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly

--
Reg me Please

pgsql-general by date:

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