August 7th, 2001, 10:21 AM
for not reinventing the wheel ... is there an out-of-the-box library for
the task is obvious: crunch sourcecode consisting mainly of function()
declarations, store the resulting string in [wherever], download the whole
enchilada through j(ava)script, decompress it, and use eval().
can anyone point me to some useful resources? any help is appreciated.
August 8th, 2001, 12:32 AM
I'm not sure what your need is, but if you have need to compress your scripts, you can compress a .js file using any old jar utility (available with any java development kit) from the command prompt.
You can then reference the compressed file in the same manner that you would reference any external .js file:
You can manually unjar the file to edit it, but there's no need (or ability for that matter) to uncompress it in your scripts.
Hope this was helpful.
August 8th, 2001, 07:55 AM
need different technique
thanks for you hints.
now, what i'd rather need is a technique which allows me to compress sourcecode and leave the compressed file in a way not too easily understandable by the average script ripper.
that means : compression + obfuscation ;o)
as i'm putting quite a heavy effort into building the application, i'm also aware of the fact that a skilled js-programmer will be able to get a clue of what's going on and extract the full code, no matter what the 'protection' is.
for that reason, i'm looking for some sort of compression which (a) provides c/c++ routines for doing the encoding in a win32 application, and (b) provides j(ava)script routines for decoding the stream.
August 9th, 2001, 12:05 AM
August 9th, 2001, 02:39 AM
Are you willing to wait?
August 9th, 2001, 02:45 AM
August 9th, 2001, 03:16 AM
What about signing scripts?