If you mean, physically, how do you do it.... you click on the Tools menu option, select EFS and then select Encrypt/Decrypt. You then select the script(s) you wish to encrypt from the list of available scripts. On the next screen, you assign a password (enter it twice in the required fields and then enter your email (or presumably any text string).
I use it quite a bit and have noticed no degradation in performance.
I've got a utility that allows encrypted files to test the users esignal ID for validation. This utility then checks an expiration date (I setup) and will allow/disallow an efs from running on a user's computer.
I paid to have this developed, but it works perfectly.
This provides me with the ability to enable/disable any EFS code for any user I want.
You can do something similar with the addEntitlement() function. You can create a file containing a list of authorized users and store it on a web site. Then, when the script it loaded by a user, it checks the file on that web site.... if the user's eSignal username is in the file, the script continues. If not, it displays an error message and halts. You can then add/remove users from the master list at any time to manage who can (and cannot) use your script.
addEntitlement() has been around for some time but only used internally by eSignal. In version 7.5 of eSignal, Matt G added the ability to monitor a user-defined authorization file which makes it a very useful tool.
As an alernative, you can also use the new HTTP() object to create a more customized authorization system.
Comment