In a recent Test Stand training session at my work, we learned about Engine callbacks and specifically about the Load and Unload ability to run code when simply loading or unloading a TS sequence file. In speaking with our FE, there is no was to disable the Engine callbacks and he asked that I post this request.
Without the ability to disable this feature, there can be inadvertent to malicious consequences. The loading or unload of a sequence file needs to be passive during development so the sequence file can be reviewed and verified to be harmless before putting the sequence file out for production use.
In the inadvertent instance, a developer could produce something that they are not quite sure will work and it could produce a side-effect. It would be good to be able to open this sequence file and review all the steps before the Engine Load callback has any chance of running.
In the malicious instance, the Engine Load could be used to perform unwanted events - I.E.. Performing a system call to format the C: drive, making a remote connection to an external computer, etc. during the code load and before anyone has a chance to review the sequence file and verify that it is harmless.
The Engine callbacks are a great feature but with the inability to disable them creates a great security risk. There needs to be an option in the TS Sequence Editor to disable all or selected Engine callbacks and then a sequence file can be opened safely and reviewed before execution.
