pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonah H. Harris <jonah.harris@gmail.com>
To: Aaron Bono <postgresql@aranya.com>
Cc: rdeleonp@gmail.com
Cc: rdeleonp@yahoo.com
Cc: pgsql-admin@postgresql.org
Subject: Re: Wrap (obfuscate) code
Date: Tue, 4 Jul 2006 18:52:17 -0400
Message-ID: <36e682920607041552h2a1ca123if24fb0eb3d65cb16@mail.gmail.com> (raw)
In-Reply-To: <bf05e51c0607041355i52167ee8qfdf719906477a376@mail.gmail.com>
References: <a55915760607041053q12a77e64je19340c0fb9e554b@mail.gmail.com>
	<36e682920607041141v1eed3239me363ac3a0ed8801c@mail.gmail.com>
	<bf05e51c0607041355i52167ee8qfdf719906477a376@mail.gmail.com>

On 7/4/06, Aaron Bono <postgresql@aranya.com> wrote:
> I don't see how PostgreSQL being open source will stop obfuscation of the
> PL/pgSQL from being possible.

You're missing the whole point.  Oracle doesn't obfuscate the code,
they compile it into bytecode and then spit the bytecode back out as a
textual "wrapped" version... this wouldn't work for an open source
database because all you'd have to do is modify the PL/pgSQL engine to
act as a code generator so that upon execution, it would nicely
generate source code to the function.  In short, childs play.

In fact, the Oracle wrap utility doesn't totally prevent you from
reverse engineering a procedure, function, or package... it just makes
it *very* difficult.  I had to do this for a company that paid a
developer to write some code for them and the consultant only gave
them the wrapped version (refusing to give them the actual source
code).  I had to reverse engineer his algorithm with nothing but
wrapped code.

Just remember, if you had the source code to Oracle, the wrap utility
would be pretty much worthless as you could easily do the same thing
as PL/pgSQL and PostgreSQL.

-- 
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: <36e682920607041552h2a1ca123if24fb0eb3d65cb16@mail.gmail.com>
Permalink:  ../36e682920607041552h2a1ca123if24fb0eb3d65cb16@mail.gmail.com/
Also on:    postgresql.org/message-id/36e682920607041552h2a1ca123if24fb0eb3d65cb16@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, postgresql@aranya.com, rdeleonp@gmail.com, rdeleonp@yahoo.com
  Subject: Re: Wrap (obfuscate) code
  In-Reply-To: <36e682920607041552h2a1ca123if24fb0eb3d65cb16@mail.gmail.com>
  References: <a55915760607041053q12a77e64je19340c0fb9e554b@mail.gmail.com> <36e682920607041141v1eed3239me363ac3a0ed8801c@mail.gmail.com> <bf05e51c0607041355i52167ee8qfdf719906477a376@mail.gmail.com> <36e682920607041552h2a1ca123if24fb0eb3d65cb16@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