Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #20431
| From | "Mel Smith" <med_cutout_syntel@aol.com> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Javascript Obfuscator problem |
| Date | 2013-06-25 08:51 -0600 |
| Message-ID | <b2tp34F7ci0U1@mid.individual.net> (permalink) |
| References | <b2rr30FpbqsU1@mid.individual.net> <kqahtq$p5l$1@news.albasani.net> |
Stefan said:
"> I'm not familiar with the JScriptProtector and JScriptCodeDom classes; a
> quick search on the web only shows other error messages like yours. My
> guess is that this obfuscator is using a home-brew parser that can't
> handle assignment lists as the first expression in |for|.
>
> This will avoid the parser error:
>
> cells = tables[i].rows[0].cells;
> nlen2 = cells.length;
> for (j = 0; j < nlen2;++j) { // ...
>
> And so do obvious syntax errors:
>
> var f o o = 4 2;
>
> (Result: "var _0x1d51=[];var f;o;o=4;21;")
>
>> Any guesses here (or is there an error my pea-brain can't find in that
>> line ) ??
>
> Your code is fine (assuming those variables are declared somewhere in
> the original code). You can either change your source to make the
> obfuscator happy, or use a different obfuscator.
Yes, the vrbls are of course defined higher-up. btw, I'm starting to
deliberately use my own 'hoisting' techniques. But maybe that's not
adviseable.
>
> That said, why are you even using an obfuscator? The only good reason
> (for carefully selected values of "good") that comes to my mind is to
> evade detection by security software. Every other use is misguided and
> counter-productive, IMHO. This includes "I don't want other people to
> see/copy my code without permission".
I'm just on a 'learning exercise', and thinking of perhaps obfuscating
the data (in the internal tables) of my pages. This has nothing to do with
JS, but, as I said, I'm just trying to get a bit of knowledge about
obfuscation techniques for later in my development. I'll be looking around
(a few months from now) about how to encrypt table data, so that the client
browser shows the info correctly, but the 'sniffer' of the table data has a
difficult time de-obfuscating.
Thanks for the response.
-Mel
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Javascript Obfuscator problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-24 15:12 -0600
Re: Javascript Obfuscator problem Stefan Weiss <krewecherl@gmail.com> - 2013-06-25 00:40 +0200
Re: Javascript Obfuscator problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-25 08:51 -0600
Re: Javascript Obfuscator problem Denis McMahon <denismfmcmahon@gmail.com> - 2013-06-25 20:46 +0000
Re: Javascript Obfuscator problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-25 15:23 -0600
Re: Javascript Obfuscator problem Andrew Poulos <ap_prog@hotmail.com> - 2013-06-26 08:15 +1000
Re: Javascript Obfuscator problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-26 17:45 -0600
Re: Javascript Obfuscator problem Andrew Poulos <ap_prog@hotmail.com> - 2013-06-27 11:58 +1000
Re: Javascript Obfuscator problem "Mel Smith" <med_cutout_syntel@aol.com> - 2013-06-27 09:10 -0600
Re: Javascript Obfuscator problem Christoph Michael Becker <cmbecker69@arcor.de> - 2013-06-27 20:49 +0200
Re: Javascript Obfuscator problem Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-06-27 21:38 +0200
Re: Javascript Obfuscator problem "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-06-25 10:45 +0200
csiph-web