Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #20442

Re: Javascript Obfuscator problem

Show all headers | View raw

Denis said:

> 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.


Hi Denis:

    I've been 'sniffing' programmatically since this past January digging 
into public web sites (to which I subscribe to and belong) that hold 
information I wish to collate and deliver to other users as a centralized 
fount of information, at the same time adding value to this public info on 
easy to read, centralized tables.  My data 'rows' now amount to 
approximately 19000+ rows of 5 columns of 'yummy' info.   These rows are 
spread among approx 67 different tables of up to 1400+ rows each -- some as 
little as ten rows.  In the process of these past six months, I have 
cleaned, and re-cleaned and programmatically corrected much of the faulty 
public information, standardized terms, standardized formats, etc, etc

    I would like to offer this new set of info to the public *free*. But, if 
it is not obscured in some fashion (thru encrypting, obfuscating, etc), then 
some *other* 'sniffer' is going to come along and take a day or so to 'lap 
up' all my hard work, and then offer it at a price.  *That* would really 
choke me up !

    So, I'd like to make that harder to do by 'obfuscating' somehow.

    Since the info is all hard textual. I thought maybe of encrypting it, 
then doing 'something' at the client browser end to de-encrypt the tables 
(thru obfuscated JS) and display in clear -- and somehow make the 'sniffer' 
work a little harder.

    But, as you note,  it would be a small task for someone with expertise 
to de-obfuscate.

Thanks.

-Mel
 

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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