N
N
NewTypes2014-01-30 23:23:51
JavaScript
NewTypes, 2014-01-30 23:23:51

Frontend obfuscation. How to hide javascript logic from the majority?

I think it makes no sense to write why.
As I see it:
- checking the domain in the script, without specifying the domain in the code (hash or something less expensive for the processor). You can bypass it, but if it's too much.
- coding the script through some kind of meat grinder-minifier, with the possibility of flexible "encryption"
- the relevance of the code in time
- tricks (connecting the left labyrinth logic or stopping normal operation - imitation of instability) when launching firebug or chrome dev tools
- specifying the license I
feel, I forgot a couple of ideas (thoughts were spinning earlier, but I didn’t write it down).

Answer the question

In order to leave comments, you need to log in

4 answer(s)
N
Nazar Mokrinsky, 2014-01-30
@nazarpc

A dead end idea that will make life difficult for both you and anyone who decides (suddenly) to use your code. It will complicate, but never exclude.
Run through a regular minifier, which obfuscates the code a little while shortening local variables, and add a license so that you have arguments in case of a conflict.
Otherwise, you won’t do anything else, if you encrypt, you still have to decrypt, which means you can get the code anyway.

E
egor_nullptr, 2014-01-30
@egor_nullptr

Try Closure first . Perhaps this will solve your problems (or some of them).

Y
Yuri Lobanov, 2014-01-31
@iiil

Yes, minifier and license. For me, that's enough so that all sorts of fools do not carry the code for lotions in their shitty website.

Z
zvorygin, 2014-01-30
@zvorygin

The presence of chrome dev tools is undetectable to my knowledge.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question