Rodrigo Sakai wrote:
>>AFAIK there's not much you can do for obfuscation of pl functions right
>>now since someone will be able to see the src text in pg_proc. However,
>>are you allowing people that you don't want to see the code access to
>>write arbitrary sql to the database?
>
> Let me explain myself a little better. Actualy we sell software, and some codes of the systems we develope here
areinside the database as functions, so we can compile the codes of the system (php, java, etc...), but not the codes
thatare in the postgresql. Some of our clientes, need that a employee of them get total access to the database instaled
locally, becoming the database administrator. Thats ok, but to protect our postgresql codes (functions) i like to
compilemy plpgsql functions, so our client's DBA will be able to do anything he wants with the database, but will not
beable to get our codes. I insist in my question, is there a way to compile the plpgsql codes or something like that,
orits better to think about writting this postgres functions in C??????
>
Security through obscurity? Why do those people you want to hide your
code from direct SQL access to the database in the first place?
Jan
> Thanks for all!!!
>
> =====================
> Rodrigo Sakai
> Database Programmer
> rodrigo@2bfree.com.br
> http://www.2bfree.com.br
> Tel: (55) (11) 5083-5577
> Fax: (55) (11) 5549-3598
> =====================
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #