Super perfect JavaScript encryption Ajax client hiding

Are you still worried about Js being viewed by customers? Is it clear That Ajax is placed on the client JS?

 

Let's take a look at my perfect JS encryption! Is it true that encryption is a disguise, but the purpose is the same ~

 

Recently, I was working on a 3 s volume system. I used a static page to upload data and generate a report,

 

Therefore, most of the processing work is left in the client JS, and the calculation formula of the entire system is all the code.

 

Anyone who wants to save the webpage will be able to get it. This is certainly a poor confidentiality. A lot of JS encryption is found on the internet, but every one of them cannot be cracked.

 

It does not conform to my perfect style of work, and the encrypted code will basically fail. I thought for a long time, I thought of a way to make the static page HTML reference the form used by JS,

 

<Script language = "JavaScript" type = "text/JavaScript" src = "http://www.zhe ***. NET/3 S/checkit. asp"> </SCRIPT>

 

Verify in checkit. asp

If instr (request. servervariables ("http_referer"), "zhe ***. net ")> 0 then // determine whether the reference page is under the domain name of this site </P> <p> response. write "document. scripts [1]. src = 'se # % ddb3sguide. JS1 </P> <p> response. write "document. scripts [0]. src = 'szb3s $ % @ te $ % s3url. JS2 </P> <p> else response. write "alert ('call error! Please return. If you need this file, please contact QQ 897564629 '); "// otherwise warning </P> <p> end if <br/>

 

People who can take this step are probably interested.

Se # % ddb3sguide. js

 

Of course, let the user know that the file name is the same and can be downloaded. Do not know whether this method can be cracked. Please advise.

 

Note: The test disguise can be cracked, and the JS still needs to be locally stored by the user. Currently, there is no good solution. solution 1 is checkit. if ASP judges that the path is illegal, it will output a garbled Code, making the hacker mistakenly think that this is only a small trap of the JS source code with deep encryption.