Re: Oracle IP and Unwrapping PL/SQL Code

From: Bill Ferguson <wbfergus_at_gmail.com>
Date: Wed, 18 Oct 2017 07:40:09 -0600
Message-ID: <CADEE6ZNA=eSaEfew14ck2e+G0xSO_Dfc1y8kDsqp7R90xV7JqA_at_mail.gmail.com>



It's been a long time since I've played with unwrapping code, but as I remember, one of the drawbacks, or at least an inconvenience, was that the comments get stripped.

Usually not that big of an issue, but depending on the skill level of the person looking at it, and what types of objects that piece of code is working with, it can quickly get extremely confusing. :)

Bill Ferguson

On Wed, Oct 18, 2017 at 7:31 AM, Rumpi Gravenstein <rgravens_at_gmail.com> wrote:

>
> I had a follow-up conversation with an Oracle product manager on this
> topic. He tells me that wrapping pl/sql should be used to identify your
> intellectual property for later legal recourse should you need it. There
> is no intention to having this actually secure anything even though that's
> not how it was originally marketed. The tone of his conversation was
> defensive with a long discourse on how even compiled code can be
> decompiled, although with a bit more effort. So ... when you see wrapped
> code consider it Oracle's version of a copyright notice.
>
> --
> Rumpi Gravenstein
>

-- 
-- Bill Ferguson

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Oct 18 2017 - 15:40:09 CEST

Original text of this message