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 3F33B9FA5DD for ; Tue, 4 Jul 2006 14:54:02 -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 87155-06 for ; Tue, 4 Jul 2006 14:53:48 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by postgresql.org (Postfix) with ESMTP id 21E529FA4A5 for ; Tue, 4 Jul 2006 14:53:47 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so1924763ugf for ; Tue, 04 Jul 2006 10:53:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Ku9nHbVqM4TswjX+rOdsQCLADLHUol13C+S9ScLpvm9ntIXOsK8Bum3qX/rutYVR6VfYeRSY6Jg2Eoja7tS8i+CbMV162QcA/ZViv53wTp5tZun3Kta8znbBM8XLfw5gQmHuh28x88x2TyUOqyf3+JxT5ShyFIVLufyT6y5ox+4= Received: by 10.67.89.5 with SMTP id r5mr6818769ugl; Tue, 04 Jul 2006 10:53:46 -0700 (PDT) Received: by 10.67.24.20 with HTTP; Tue, 4 Jul 2006 10:53:46 -0700 (PDT) Message-ID: Date: Tue, 4 Jul 2006 12:53:46 -0500 From: "Rodrigo De Leon" Reply-To: rdeleonp@gmail.com, rdeleonp@yahoo.com To: pgsql-admin@postgresql.org Subject: Wrap (obfuscate) code MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/11 X-Sequence-Number: 22257 Good afternoon. I'm not sure if this is the correct list, so please forgive me if it's not. 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: http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96624/c_wrap.htm#LNPLS016 Thanks for your time. Regards, Rodrigo