Securing stored procedures and triggers - Mailing list pgsql-general

From mgould
Subject Securing stored procedures and triggers
Date
Msg-id 20071031143955.83616a2d@mail.allcoast.net
Whole thread Raw
Responses Re: Securing stored procedures and triggers  (Reg Me Please <regmeplease@gmail.com>)
Re: Securing stored procedures and triggers  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Re: Securing stored procedures and triggers  (Douglas McNaught <doug@mcnaught.org>)
Re: Securing stored procedures and triggers  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-general
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?


Best Regards,

Michael Gould
All Coast Intermodal Services, Inc.
904-376-7030

pgsql-general by date:

Previous
From: David Fetter
Date:
Subject: Re: Updated .vim file
Next
From: "Moisan Yves"
Date:
Subject: Re: PG windows service issues