pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonah H. Harris <jonah.harris@gmail.com>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org, "Aaron Bono" <postgresql@aranya.com>
Cc: rdeleonp@gmail.com
Cc: rdeleonp@yahoo.com
Subject: Re: Wrap (obfuscate) code
Date: Wed, 5 Jul 2006 09:10:32 -0400
Message-ID: <36e682920607050610t1eb0a17fxe9b8d1c756919d20@mail.gmail.com> (raw)
In-Reply-To: <200607041656.19430.jd@commandprompt.com>
References: <a55915760607041053q12a77e64je19340c0fb9e554b@mail.gmail.com>
	<36e682920607041552h2a1ca123if24fb0eb3d65cb16@mail.gmail.com>
	<36e682920607041553g28cc72b5p2a0dc5eec26a357a@mail.gmail.com>
	<200607041656.19430.jd@commandprompt.com>

On 7/4/06, Joshua D. Drake <jd@commandprompt.com> wrote:
> Although everything you say is accurate Jonah, it will cost more money to
> defang obfuscated code then non obfuscated code. Thus there is a financial
> detterant to stealing.

My bet is that it would take < 1 day to turn PL/pgSQL into a code
generator, thereby making both the obfuscation and bytecode methods
practically worthless.

I agree with Tom... if you want to hide the code just write it in C.
Of course, you could always take the "proprietary" shell script
approach and hide the PL/pgSQL in C code so that, upon execution, the
C code generates and calls the PL/pgSQL function and removes it on
exit... but still, it wouldn't really be that hard to get around it.

I've used Oracle's wrap utility on several products, but I've never
really felt that it secured our code... just made it *very* difficult
to decompile.  I've never used obfuscation because I know how easy it
is to hack one of the C or Java compilers to make the code much more
readable and understandable.  Just my 2 cents... but if someone wants
to add obfuscation functionality to PL/pgSQL, by all means go for it.

-- 
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation            | fax: 732.331.1301
33 Wood Ave S, 2nd Floor            | jharris@enterprisedb.com
Iselin, New Jersey 08830            | http://www.enterprisedb.com/



view thread (14+ messages)  latest in thread

Message-ID: <36e682920607050610t1eb0a17fxe9b8d1c756919d20@mail.gmail.com>
Permalink:  ../36e682920607050610t1eb0a17fxe9b8d1c756919d20@mail.gmail.com/
Also on:    postgresql.org/message-id/36e682920607050610t1eb0a17fxe9b8d1c756919d20@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jonah.harris@gmail.com, jd@commandprompt.com, postgresql@aranya.com, rdeleonp@gmail.com, rdeleonp@yahoo.com
  Subject: Re: Wrap (obfuscate) code
  In-Reply-To: <36e682920607050610t1eb0a17fxe9b8d1c756919d20@mail.gmail.com>
  References: <a55915760607041053q12a77e64je19340c0fb9e554b@mail.gmail.com> <36e682920607041552h2a1ca123if24fb0eb3d65cb16@mail.gmail.com> <36e682920607041553g28cc72b5p2a0dc5eec26a357a@mail.gmail.com> <200607041656.19430.jd@commandprompt.com> <36e682920607050610t1eb0a17fxe9b8d1c756919d20@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox