 "We've tried others - ASE reigns supreme. Maybe your complex script requires more than just the script file to make it work, maybe you've created a work product that you would rather not have others steal/hack, or maybe you need to run your script with a different set of credentials. Script Packager lets you deploy your script product in a tidy executable format, configured to properly launch with the right script engine, including all the additional files you need, encrypted for enhanced security, and launched with alternative credentials: adds a highly professional feel to your hard work."
--Dx21.com
 The Script Packager™ provides the ability
create secure executable packages from your scripts and offers the
following capabilities:
-
Run As Support* - specify
an alternate account for the execution of the script.
- Include Support Files -
resource kit tools, command interpreters, data files - whatever your
script needs may be included right inside your the executable
package.
- Encrypted Executable - the
executable package itself is encrypted.
- File Protection During
Execution* - Using NTFS and EFS
- Event Logging - optionally
log success or failure in Windows Event log.
- Return Codes - packaged
executable will return any error it encounters as a return code, or
if there are no problems, it will return that of the script being
executed.
- Command-line Parameter Support
- Have your packaged script accept command line parameters and
write your own command line utilities!
- Optional System Tray Icon
During Execution - even specify a tool-tip message to advise
your users your script is running.
- Customize Icons - for the
system tray icon or for the executable package itself
* Security features require Windows
2000 or later on target system
About Encryption
While the data is contained inside of the executable package, all data is
encrypted with Triple DES and all cryptographic hashing is done via RC4.
During execution, the script (and all additional data) is unpacked,
decrypted and is available in plain text for use on the local drive where it
is extracted.
To protect this data during and after extraction you can turn on the
'alternate credentials' feature of the script packager which enables use of
both NTFS permissions (minimally effective by itself) and EFS encryption
(must stronger protection). This will ensure that no one will be able to
view/edit the extracted contents of the package. Even the user who launches
the package will not be able to view/edit the data directly. Once EFS is
applied to the data it can only be viewed by an authorized EFS recovery
agent for the domain or the user whose credentials were used during package
creation.
|
|
)
