Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #20440
| From | Denis McMahon <denismfmcmahon@gmail.com> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Javascript Obfuscator problem |
| Date | 2013-06-25 20:46 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <kqcvjv$3j3$5@dont-email.me> (permalink) |
| References | <b2rr30FpbqsU1@mid.individual.net> <kqahtq$p5l$1@news.albasani.net> <b2tp34F7ci0U1@mid.individual.net> |
On Tue, 25 Jun 2013 08:51:09 -0600, Mel Smith wrote: > 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. Anything that is genuinely worth the effort of obfuscating is worth the effort of cracking. Furthermore, some people will, on detecting your obfuscation, simply crack it to see what you're hiding. It is the very nature of the web that by using wget I can invariably get the raw data that a server sends, regardless of cookies, browser sniffing, ajax etc at the server. Once I have the data, I can de-obfuscate it. Alternatively, I can use greasemonkey to write a script that walks the dom. This is assuming that saving the whole web page or simply copying and pasting from the screen won't do the job. You are wasting your time if you are trying to obfuscate data from the end user whose browser you are planning to deliver it to. If you need to protect it in transit, use https. -- Denis McMahon, denismfmcmahon@gmail.com
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