Scripts Encryptor
F.A.Q. Home
Icon:
Here are some Frequently Asked Questions asked through this web site:
  Q: Who is the author of the software available to download on this web site?
A: Every software product available for downloading on this website was designed and coded by Dennis A. Babkin, David Chon, Richard Casokane with indispensable assistance of our team and supporters.
  Q: What is the experience of the authors of the software?
A: I [Dennis] will answer for myself. I have been involved in C/C++/MFC programming since 1997 when I started taking classes in the Object Oriented Programming in my college. Now I have a Master's Degree in computer programming and my knowledge and expertise include: C, C++, MFC, x86 Assembly, HTML/DHTML, Php, SQL/MySQL, and much more.
  Q: Why software on this web site is not freeware?
A: Well it's a rhetorical question - why do we have to pay for food in a supermarket when we can forage for it:) To be serious, this small charge we ask for the use of our software will be spent for new development and to support of our team. Besides that, being students ourselves, we understand "educational" purpose of downloading our software. That is why such products as WinID and TOff are provided absolutely free of charge. Moreover you can download TOff's source code free of charge if you want to learn how that program works.
  Q: If I buy any of the software product licenses here will I be entitled for promotions and discounts?
A: Yes, absolutely. Besides showing your support for our team and for future developments you will be entitled for free updates for future versions of the software. Any other information will be included in the license agreement for a particular software product.
  Q: How strong is encryption performed by Scripts Encryptor?
A: That is a good question. Many people confront us with the fact that Scripts Encryptor does not provide strong encryption of Java Script and HTML. Well, let me tell you, to be exact it does not provide encryption at all. What it does, it obfuscates, or scrambles the code that makes it hard (but, let me stress, not impossible) to decode or reverse engineer your script or page. You might be incensed now after reading this. Well, don't blame us, we did not invent scripting language for web browsers. Unfortunately for all developers, client side scripts do not allow any encryption, so the only way to protect client-side content is to scramble it to make it harder for somebody to steal your work or meddle with it. Do not believe anybody who says that their product will encrypt your client-side web page - this is not true. My main point of using Scripts Encryptor is to compress and scramble code, but not to encrypt it!
  Q: I have encoded the JS file, but I can decode it back to a readable file on any version of your software. I realize that it should be decodable in order for IE to read it but it just worries me that if I encode it that anybody can decode it?
A: I understand your concern about protection of JS files. Unfortunately, at the current time there is no known encryption of JavaScript and/or HTML to be at least as secure as compiling of C source code into executable files. Due to limitations imposed by web browsers the only way to hide your code would be to scramble it into blocks of code unreadable for humans. Our product provides means for that.

Since during processing the web browser has to interpret each line of code in your script, there might be some other programs that can do the same "interpretation" (i.e. de-scrambling) as well. Scripts Encryptor is no novelty here either. It just incorporates features in many other products available online and bundles them into one package. Again, I want to repeat that there is no known way to encrypt JS or HTML files to be inaccessible by hackers and advanced users. The main goal of using our product should be an attempt to either optimize JS files to improve performance, or scramble them to protect against an average intruder.

As a suggestion I'd strongly recommend to separate your code into two sections: server and client side. Put all the sensitive information on the server (which should not necessarily have a strong encryption of the script files) and all the rest to the client side, downloadable to a user's machine. So far, this is the only sure way to protect your web sites against intrusion.
  Q: What is the difference between version for Windows 95/98/ME and Windows NT/2000/XP?
A: We have discontinued the version of Scripts Encryptor for Windows 95/98/ME due to lack of demand. These operating systems are pretty much obsolete now. For backward compatibility we still provide an older version of Scripts Encryptor for those systems. To utilize the best in Scripts Encryptor please download the latest version for Windows NT/2000/XP.
  Q: I have the following code snippet, how can I obfuscate JavaScript part?

<html>
<head>
<script type="text/javascript">
<!--
    //Part I want to scramble
    function DoIt()
    {
        var v = "This is the string I want to be scrambled";
        alert("Scrambled OK\nHere is the string:\n\n" + v);
    }
    //End of part that I want to scramble
-->
</script>
</head>
<body>
<script type="text/javascript">
<!--
    DoIt();
-->
</script>
</body>
</html>
A: There are three ways this could be done:
  1. Start Scripts Encryptor, or click "Clear 'Before'" if it's already running. Copy the whole snippet (from <html> tag to </html> tag) into 'Before' window of Scripts Encryptor. Select 'HTML + JavaScript' in the Type field. Select other appropriate conversion settings, including "Encode Script". Make sure "Scramble" is selected in the Operation field. Click Convert button. 'After' window will now have scrambled code. Simply copy and paste it back to your HTML editor, or save it as HTML file right from Scripts Encryptor. (Please note, that 'Scramble' selection will also scramble HTML tags on this page. To avoid changing HTML use 'No changes' option in the Operation field.)
     
  2. Start Scripts Encryptor, or click "Clear 'Before'" if it's already running. Copy desired JavaScript part (everything between <!--  and --> in the first <script> and </script> tags, marked green in the sample above) into 'Before' window of Scripts Encryptor. Select 'JavaScript' in the Type field. Select other appropriate conversion settings, including "Encode Script". Make sure "Scramble" is selected in the Operation field. Click Convert button. 'After' window will now have scrambled code. Copy entire contents of the 'After' window and paste it back in place of the initial JavaScript segment preserving <script>, </script> tags. Remove <!-- and --> tags. Change <script> block to <script language="JScript.Encode">. The resulting HTML should look like this: (Do not copy block below to your HTML editor as it will give out errors since some encoded characters could not be displayed here!)
     <html>
    <head>
    <script language="JScript.Encode">
    #@~^+AAAAA==W!x^DkKxPGW&O`* -lMP-xrKtbd-!!!yTwFlFk-TcTw!!TGWwEZ!0'E!Tl-;!Z+Z/O'EZ!Gyk wFWGw!W!(wZc!';!ZGG'q*F Y'!*!w;Z!{cK~-!!Ty-ETT+*w!WTkmw!!ZG m-!T!+N8V'ETT+*-8*cril^n.YvJUm.-;TZvq:(s+9P6F'xCnw!!TGyn,-;Z!+,/'EZT ZY4+'ETTy!-!T!F&Y'q bx'F*Gw;Z!fl'U- JQ-*89EgAAA==^#~@
    </script>
    </head>
    <body>
    <script type="text/javascript">
    <!--
        DoIt();
    -->
    </script>
    </body>
    </html>
     
  3. Start Scripts Encryptor, or click "Clear 'Before'" if it's already running. Copy desired JavaScript part (everything between <!--  and --> in the first <script> and </script> tags, marked green in the first sample above) into 'Before' window of Scripts Encryptor. Select 'JavaScript' in the Type field. Select other appropriate conversion settings, including "Encode Script". Make sure "Scramble" is selected in the Operation field. Click Convert button. 'After' window will now have scrambled code. Click "Save 'After' window" button and save it as "temp.js" file in the same folder where you will be running the HTML sample. Change entire first <script> </script> block to <script language="JScript.Encode" src="temp.js"></script>. The resulting HTML should look like this:
     <html>
    <head>
    <script language="JScript.Encode" src="temp.js"></script>
    </head>
    <body>
    <script type="text/javascript">
    <!--
        DoIt();
    -->
    </script>
    </body>
    </html>
The 3rd way is more preferable as it saves scrambled data in a separate file, which prevents unintentional alteration of one of the encoded symbols in the HTML editor. You can also use 1st method to scramble page ready for posting on your website. Fore more information please refer to the Manual or the Samples Page.
  Q: I tried encoding JavaScript using "Encode Script" option. It works good in Internet Explorer but will it work in other browsers?
A: Unfortunately, the answer is no. At the current stage, only Microsoft Internet Explorer version 5.0 and later supports encoded JavaScript blocks. Please make sure that this is only attributed to JavaScript encoded using "Encode script" option. The rest of obfuscation is browser-independent. This should not deter you from using this feature though. Just make sure that you create two versions of the same page and make your server side software detect client browser. If it's Microsoft Internet Explorer then make it send encoded version of your page, otherwise send a regular page.
  Q: [Unaltered text] did u have a little kid make this program because it totally sucks how in the hell do u expect peopl to pay for something this dumb? how in the hell can this program protect source code when i encoded an html document with some vb and js scripts and after it decoded it, i copied it to frontpage just to see how encoded it really was, and guess what, frontpage had no problem decoding it because all that your program did was just converted it to anci characters. so what am i trying to tell u is that if u want money for your so-called hard work, i highly suggest u work alittle bit harder on your programs, although you could've even taken source code from someone else like a little kid because the program is crap and thats it.
A: I don't think it's really a question, but let me respond anyway.

(1) No, we do not employ child labor to write our software products. It is illegal in the US, which I'm not sure about the place you're from.

(2) You should better read documentation, as it clearly states that Scripts Encryptor does not work with Visual Basic scripts. As for HTML, we've said many times that by design it does not allow much of encryption. Main goal of using Scripts Encryptor is to scramble some of the contents, but not to protect it. There is big difference in it.

(3) If you looked at Scripts Encryptor a little bit longer you'd see that there are settings in its main window that allow different degrees of obfuscation. By default, right after installation they are set up to a low level of scrambling. Before making any claims one should attempt changing those settings according to preferred results -- we thought it was obvious for an intelligent person.

(4) As for FrontPage being able to "decode" our scrambled code, I'm not sure I understand what you mean, as FrontPage does not decode anything. All it does, it displays your web page and allows you to visually edit it. If you meant seeing your web page in FrontPage, then it is actually what we intended to achieve -- making HTML hard to read and easy/fast to load in the web browser.

(5) There are many other obfuscators available on the web. We let you evaluate it but we do not make anybody pay for our software. We try to keep the one-time charge to a minimum. But, if you don't like our product simply discontinue using it.

We still appreciate any kind of feedback that you send to us.
To ask your own question: Please use our feedback page.

 
This is the private web site. Copyright (c) 2003-2010
Last updated: September 3, 2010