Re: Wrap (obfuscate) code

On Tuesday 04 July 2006 15:53, Jonah H. Harris wrote:
> On 7/4/06, Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com> wrote:
> > On 7/4/06, Aaron Bono <postgresql(at)aranya(dot)com> wrote:
> > > I don't see how PostgreSQL being open source will stop obfuscation of
> > > the PL/pgSQL from being possible.
>
> Oh, and I forgot to add, obfuscation is lame and doesn't really work.
> Anyone with a good amount of compiler knowledge can easily get past
> obfuscated code. But hey, if it makes you feel like you've protected
> yourself, by all means... obfuscate away :)

Obfuscation is good in the sense that it can allow a person paying for code
to have a reasonable piece of mind that their customers can't just open the
jar and steal the cookies.

Although everything you say is accurate Jonah, it will cost more money to
defang obfuscated code then non obfuscated code. Thus there is a financial
detterant to stealing.

I have more then once been in an environment where, "Oh we just "sampled" the
function from *xyz*".

Sincerely,

Joshua D. Drake