Unwrapping PL/SQL code

by Granville Bonyata on January 24, 2012

For years the Oracle line was that a software vendor could safely send out its PL/SQL code if it was wrapped. I’m sure I was not alone in thinking that we could hide sensitive code like the application’s licensing enforcement inside Oracle’s wrapper.

Turns out this isn’t the case. It has been unwrapped a number of times, most prominently (and publicly) at www.codecrete.net/UnwrapIt.

Oracle’s response? Here’s Tom Kyte:
“Using the latest wrap would provide the highest degree of ‘protection’. That is all.
I put ‘protection’ in quotes because I’ve always been amused by ‘wrapping’ code.”

So when an Oracle feature doesn’t work, Oracle’s response is that it was amusing that you ever wanted to use that feature in the first place.

Previous post:

Next post: