Protecting EFS Scripts in eSignal (Part 1)

A question we frequently get from eSignal users who are building their own EFS indicators is "How can I protect the source code?".

Note: this discussion assumes you are running eSignal 12.x or newer

There are a few options depending upon your ultimate goal:

• Encryption only;
• Encryption and basic licensing control;
• Encryption and enhanced licensing control;

Encryption Only

If you encrypt an eSignal EFS script, it will allow the script to be run in any eSignal chart (or watchlist) by any user, but it will prevent the actual source code from being displayed or changed if someone loads the script into any text editor (i.e., the eSignal script editor, notepad, etc.). So, encryption-only protects the source code from prying eyes but it will not restrict who can run your indicator.

To encrypt an EFS script:

• Add the setProperty( "HideEncryptedLock", "yes" ); line into the preMain() section of your EFS script and save the file;
• In the eSignal Script Editor (New/Script Editor from the menu) load the EFS file if it is not already loaded and then click on the Verify button on the Editor top toolbar. If it passes the test then click on the Encrypt button which is right next to the Verify button;
• A new EFS file will be created in the same folder as the original but with the string "_encrypted" added to the end of the file name;
• At this point you can rename the EFS file to whatever you want and distribute it. Just be sure not to overwrite the original, non-encrypted version! Always keep the original, source-code version in a safe place as there is no way to un-encrypt a EFS script.

To be Continued in the next Post....

Divergence Software, Inc.
www.sr-analyst.com
support@sr-analyst.com
Contact Us/Subscribe