6 Replies Latest reply on Nov 13, 2012 6:56 PM by pe*432630*te

    pl/sql code Security

      How to get users pl/sql code Security.
      wrap is not a safe option.
        • 1. Re: pl/sql code Security
          Lakmal Rajapakse
          Pete Finnigan has a tool to secure PL/SQL - see:

          • 2. Re: pl/sql code Security
            I is a good way.
            • 3. Re: pl/sql code Security
              where to download?
              • 4. Re: pl/sql code Security
                Harm Joris ten Napel-Oracle

                typically any problems when the database has difficulty running wrapped code that was altered after the
                oracle supported wrap took place (step 4 on the listed url) would not be supported, it's not recommended
                or supported to alter already wrapped code,


                • 5. Re: pl/sql code Security
                  dfy167 wrote:
                  where to download?
                  It's a commercial tool. It doesn't appear that the links to purchase a license are working. I assume that if you email info at petefinnigan dot com that they'll get back to you with information about how to license the tool and/or how to arrange a demo.

                  • 6. Re: pl/sql code Security
                    Hi Guys,

                    Very late response but someone just made me aware of this thread. All the links on http://www.pfclobfuscate.com now work and the site includes licensing details and prices.

                    The tool set can be used with link 4 or not; its really up to the users choice; so you can simply obfuscate or you can also wrap and wrapprotect. The WrapProtect makes the Oracle wrap file not unwrappable by known unwrappers. The only way to acheive this is by changing the wrap output. Strictly speaking the modified wrap output is only used to compile the PL/SQL into the database and thereafter the compiled PL/SQL is executed not the wrapped file output. Therefore as long as it compiles its pretty safe to run; but a user of PFCLOBfuscate/WrapProtect should test. The balance is to get security of your IPR in your PL/SQL; so far we have quite a number of clients using these tools to protect their PL/SQL code from being read by unauthorised people. drop me an email if you would like a demo of how it works; no obligations at all.

                    Kind regards