Erik has a valid point - at work we use some JavaScript obfuscation in conjunction with a PDF time-out plug-in. Basically we have the plug-in timeout one year after installation, which is a not-so-gentle nudge to get our customers to run out and buy a new version of our product. It's heinous, but it does work. And most of our clients don't have the technical level to reverse engineer, so it works rather well in this instance.
Personally I try to use JavaScript as little as humanly possible. � ----- What would happen if an irresistible force ran into an immovable object? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erik > Curiel > Sent: Friday, March 12, 2004 3:29 PM > To: [EMAIL PROTECTED] > Subject: Re: [Bits] javascript obfuscator > > > > > :obfuscation of js is pointless. > > > > How so? > > The only reason I can think of to obfuscate is to improve security or to > protect intellectual property. If you have valuable IP or sensitive > security matters in js, you're doing something mighty wrong. > > E > > -- > Erik Curiel > almost software-architect/would-be philosopher > > "... there has never been an intelligent person over the age of sixty who > would consent to live his life over again. His or anyone else's." > > -- Mark Twain, "Letters from the Earth" > > _______________________________________________ > Bits mailing list > [EMAIL PROTECTED] > http://www.sugoi.org/mailman/listinfo/bits _______________________________________________ Bits mailing list [EMAIL PROTECTED] http://www.sugoi.org/mailman/listinfo/bits
