X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id AFC8F9FA4A5 for ; Tue, 4 Jul 2006 17:55:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 13057-05 for ; Tue, 4 Jul 2006 17:55:25 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by postgresql.org (Postfix) with ESMTP id CF5439FA0EC for ; Tue, 4 Jul 2006 17:55:23 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id c29so1173683nfb for ; Tue, 04 Jul 2006 13:55:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=c80/AmevKre05eV0Zy9RQaerSAQVl/6xPdWaLg0ApgwQTTSiiU0lFWDlwMGJZC6W1bjRAo/6Fb5M+yURgUk4/VS5WkAcbAIaN2tUGuiJbuRj1LnAS6wIT5u59b+OZHiovhUNWwAPGa2yX2EivPuVLACVnGybEDacbmTpZKlbNyk= Received: by 10.78.139.5 with SMTP id m5mr2919809hud; Tue, 04 Jul 2006 13:55:19 -0700 (PDT) Received: by 10.78.29.2 with HTTP; Tue, 4 Jul 2006 13:55:19 -0700 (PDT) Message-ID: Date: Tue, 4 Jul 2006 15:55:19 -0500 From: "Aaron Bono" To: "Jonah H. Harris" Subject: Re: Wrap (obfuscate) code Cc: rdeleonp@gmail.com, rdeleonp@yahoo.com, pgsql-admin@postgresql.org In-Reply-To: <36e682920607041141v1eed3239me363ac3a0ed8801c@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_62174_33188627.1152046519056" References: <36e682920607041141v1eed3239me363ac3a0ed8801c@mail.gmail.com> X-Google-Sender-Auth: ed3631cfc30b12d6 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/16 X-Sequence-Number: 22262 ------=_Part_62174_33188627.1152046519056 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/4/06, Jonah H. Harris wrote: > > On 7/4/06, Rodrigo De Leon wrote: > > I was wondering if there's a mechanism (or if not, a workaround) to > > obfuscate server code (PL/PgSQL), a la Oracle's PL/SQL Wrap Utility: > > No, there is no such utility for PostgreSQL. And, even if there were, > it wouldn't actually stop someone from reverse engineering it quite > easily as the source code to PL/pgSQL itself is readily available. I don't see how PostgreSQL being open source will stop obfuscation of the PL/pgSQL from being possible. Sure you can look at the code for a stored procedure but the point of obfuscation is to make it hard to understand, not impossible to see. A very long stored procedure could be quite difficult to read if it were obfuscated well - that would not stop someone from being able to understand what you did, just make it so hard that it would be unlikely that it is worth the effort. -Aaron ------=_Part_62174_33188627.1152046519056 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/4/06, Jonah H. Harris <jonah.harris@gmail.com> wrote:
On 7/4/06, Rodrigo De Leon <rdeleonp@gmail.com> wrote:
> I was wondering if there's a mechanism (or if not, a workaround) to
> obfuscate server code (PL/PgSQL), a la Oracle's PL/SQL Wrap Utility:

No, there is no such utility for PostgreSQL.  And, even if there were,
it wouldn't actually stop someone from reverse engineering it quite
easily as the source code to PL/pgSQL itself is readily available.


I don't see how PostgreSQL being open source will stop obfuscation of the PL/pgSQL from being possible.  Sure you can look at the code for a stored procedure but the point of obfuscation is to make it hard to understand, not impossible to see.  A very long stored procedure could be quite difficult to read if it were obfuscated well - that would not stop someone from being able to understand what you did, just make it so hard that it would be unlikely that it is worth the effort.

-Aaron

------=_Part_62174_33188627.1152046519056--