2010/6/24 Joshua D. Drake <jd@xxxxxxxxxxxxxxxxx>: > On Thu, 2010-06-24 at 22:18 +0100, Dave Page wrote: > >> > I have no problem with him trying to protect his hard earned work. I >> > just think he is trying to solve the wrong problem. >> >> It's a real problem faced by many businesses and solved by most >> commercial DBMSs. Of course, it's basically impossible to solve in the >> Open Source world, as there's nowhere to hide a key or obfuscation >> algorithm. If akp geek is able to use EnterpriseDB builds of Postgres, >> then he may want to look at PL/Secure, which will obfuscate his >> pl/pgsql code: >> >> http://www.enterprisedb.com/products/pl_secure_standard_server.do > > That's interesting... does it just turn it into bytecode? > probably it doesn't - but it is a black box. So some minimal protection is possible :) Pavel > Joshua D. Drake > >> > > -- > PostgreSQL.org Major Contributor > Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 > Consulting, Training, Support, Custom Development, Engineering > > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
